diff --git a/sqlite3-6216bfcb.patch b/sqlite3-6216bfcb.patch
new file mode 100644
index 0000000..bc6c382
--- /dev/null
+++ b/sqlite3-6216bfcb.patch
@@ -0,0 +1,46 @@
+Index: test/fts3corrupt4.test
+==================================================================
+--- test/fts3corrupt4.test
++++ test/fts3corrupt4.test
+@@ -4401,14 +4401,36 @@
+ do_catchsql_test 25.5 {
+   WITH RECURSIVE c(x) AS (VALUES(1) UNION ALL SELECT x%1 FROM c WHERE x<599237)
+     INSERT INTO t1( a ) SELECT randomblob(3000) FROM t2 ;
+ } {0 {}}
+ 
+-do_catchsql_test 25.6 {
+-  INSERT INTO t1(t1) SELECT x FROM t2;
+-  INSERT INTO t1(t1) SELECT x FROM t2;
+-} {1 {database disk image is malformed}}
++if {$tcl_platform(byteOrder)=="littleEndian"} {
++  # The SQLITE_CORRUPT error depends on the specific random byte
++  # sequence generated by SQLite's PRNG.  But the SQLite PRNG
++  # uses ChaCha20, which generates a different byte sequence on
++  # big-endian and little-endian platforms.  The SQLITE_CORRUPT
++  # error only comes up when the pseudo-random byte sequence is
++  # the one generated on little-endian platforms.
++  #
++  # See Forum thread:
++  # https://sqlite.org/forum/forumpost/b5f89d813babfd88
++  #
++  do_catchsql_test 25.6a {
++    INSERT INTO t1(t1) SELECT x FROM t2;
++  } {1 {database disk image is malformed}}
++  do_catchsql_test 25.6b {
++    INSERT INTO t1(t1) SELECT x FROM t2;
++  } {1 {database disk image is malformed}}
++} else {
++  do_catchsql_test 25.6a {
++    INSERT INTO t1(t1) SELECT x FROM t2;
++  } {0 {}}
++  do_catchsql_test 25.6b {
++    INSERT INTO t1(t1) SELECT x FROM t2;
++  } {0 {}}
++}
++
+ 
+ #-------------------------------------------------------------------------
+ reset_db
+ do_test 26.0 {
+   sqlite3 db {}
+
diff --git a/sqlite3.changes b/sqlite3.changes
index 2e0b0ab..0c4d5cc 100644
--- a/sqlite3.changes
+++ b/sqlite3.changes
@@ -1,3 +1,10 @@
+-------------------------------------------------------------------
+Mon Dec 16 15:40:43 UTC 2024 - Reinhard Max <max@suse.com>
+
+- Add sqlite3-6216bfcb.patch to fix a test suite regression in
+  3.47.0 on s390x. Only the test was broken, not the code itself.
+  https://sqlite.org/forum/forumpost/7b2bab04c5
+
 -------------------------------------------------------------------
 Mon Dec  9 11:26:23 UTC 2024 - Reinhard Max <max@suse.com>
 
diff --git a/sqlite3.spec b/sqlite3.spec
index 6dd701b..dead6df 100644
--- a/sqlite3.spec
+++ b/sqlite3.spec
@@ -31,6 +31,7 @@ URL:            https://www.sqlite.org/
 Source0:        https://www.sqlite.org/2023/sqlite-src-%{tarversion}.zip
 Source1:        baselibs.conf
 Source2:        https://www.sqlite.org/2023/sqlite-doc-%{docversion}.zip
+Patch0:         sqlite3-6216bfcb.patch
 BuildRequires:  automake
 BuildRequires:  libtool
 BuildRequires:  pkgconfig