mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-08-20 00:49:34 +02:00
Code Issues Packages Projects Releases Wiki Activity

sqlite3: fix CVE-2026-11822 and CVE-2026-11824

Browse Source 
This patch applies the upstream fix [1], which addresses memory
corruption vulnerabilities in the SQLite FTS5 full-text search extension.
The GitHub mirror commit [1] corresponds to the SQLite Fossil check-in
shown in [2].

[1] e0b995b2a6
[2] https://sqlite.org/src/info/061febcf41ca

Reference:
https://nvd.nist.gov/vuln/detail/CVE-2026-11822
https://nvd.nist.gov/vuln/detail/CVE-2026-11824

(From OE-Core rev: 3de44d1dd09907f620ed349dba563c489a5cecb9)

Signed-off-by: Deepak Rathore <deeratho@cisco.com>
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Paul Barker <paul@pbarker.dev>
This commit is contained in:
Deepak Rathore
2026-07-23 19:13:40 +05:30
committed by Paul Barker
parent 8e0b74b1d8
commit f1d5865685
2 changed files with 42 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
meta/recipes-support/sqlite/sqlite3/CVE-2026-11822_CVE-2026-11824.patch Normal file
View File

@@ -0,0 +1,41 @@
From ceece94b0040125a12192f6f23b1ec413871b04c Mon Sep 17 00:00:00 2001
From: drh <>
Date: Mon, 11 May 2026 12:00:19 +0000
Subject: [PATCH] Fix potential buffer overwrite that could occur in fts5 when
processing corrupt records.
FossilOrigin-Name: 061febcf41ca4872a0f407951e1507209daca7895122b909a7806c60b6e200c4
CVE: CVE-2026-11822 CVE-2026-11824
Upstream-Status: Backport [https://github.com/sqlite/sqlite/commit/e0b995b2a62b78979eb65bb8dadfa912eaa8e62f]
Backport Changes:
- Applied the upstream fts5LeafRead() fix from ext/fts5/fts5_index.c
to sqlite3.c because the Yocto sqlite-autoconf source uses the
amalgamated SQLite layout.
- Omitted ext/fts5/test/fts5corruptA.test because this extracted
recipe source contains the SQLite autoconf/amalgamation layout and
does not carry the upstream Tcl test tree.
- Omitted Git mirror metadata files manifest and manifest.uuid because
they are not required for the security fix in this source layout.
Signed-off-by: Deepak Rathore <deeratho@cisco.com>
---
sqlite3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sqlite3.c b/sqlite3.c
index fb42adcd7..6acf46a5b 100644
--- a/sqlite3.c
+++ b/sqlite3.c
@@ -239694,7 +239694,7 @@ static void fts5DataRelease(Fts5Data *pData){
static Fts5Data *fts5LeafRead(Fts5Index *p, i64 iRowid){
Fts5Data *pRet = fts5DataRead(p, iRowid);
if( pRet ){
- if( pRet->nn<4 || pRet->szLeaf>pRet->nn ){
+ if( pRet->szLeaf<4 || pRet->szLeaf>pRet->nn ){
p->rc = FTS5_CORRUPT;
fts5DataRelease(pRet);
pRet = 0;
--
2.51.0

1
meta/recipes-support/sqlite/sqlite3_3.45.3.bb
View File

@@ -9,6 +9,7 @@ SRC_URI = "http://www.sqlite.org/2024/sqlite-autoconf-${SQLITE_PV}.tar.gz \
file://CVE-2025-6965.patch \
file://CVE-2025-7709.patch \
file://CVE-2025-70873.patch \
file://CVE-2026-11822_CVE-2026-11824.patch \
"
SRC_URI[sha256sum] = "b2809ca53124c19c60f42bf627736eae011afdcc205bb48270a5ee9a38191531"