Skip to contentSkip to conversation

glibc: stable 2.38 branch updates.

PATCH In review [email protected] 4 participants 5 messages Oct 3, 2023 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

PATCH v3 1/1 glibc: stable 2.38 branch updates.

From: Deepthi Hemraj <[email protected]>

Below commits on glibc-2.38 stable branch are updated.
0e1ef6779a (HEAD -> release/2.38/master, origin/release/2.38/master) manual/jobs.texi: Add missing @item EPERM for getpgid d94461bb86 string: Fix tester build with fortify enable with gcc < 12
63250e9c57 iconv: restore verbosity with unrecognized encoding names (bug 30694)
00ae4f10b5 getaddrinfo: Fix use after free in getcanonname (CVE-2023-4806)
b25508dd77 CVE-2023-4527: Stack read overflow with large TCP responses in no-aaaa mode
89da8bc588 NEWS: Add the 2.38.1 bug list
d3ba6c1333 elf: Move l_init_called_next to old place of l_text_end in link map
750f19526a elf: Remove unused l_text_end field from struct link_map
a3189f66a5 elf: Always call destructors in reverse constructor order (bug 30785)
7ae211a01b elf: Do not run constructors for proxy objects
92201f16cb libio: Fix oversized __io_vtables
5bdef6f27c io: Fix record locking contants for powerpc64 with __USE_FILE_OFFSET64

0024-CVE-2023-4527.patch is dropped

---
 meta/recipes-core/glibc/glibc-version.inc     |   2 +-
 .../glibc/glibc/0024-CVE-2023-4527.patch      | 219 ------------------
 meta/recipes-core/glibc/glibc_2.38.bb         |   1 -
 3 files changed, 1 insertion(+), 221 deletions(-)
 delete mode 100644 meta/recipes-core/glibc/glibc/0024-CVE-2023-4527.patch
meta/recipes-core/glibc/glibc-version.inc +1 -1
index a907444f50..f5ebbb2ee6 100644
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.38/master"
 PV = "2.38+git"
-SRCREV_glibc ?= "1aed90c9c8f8be9f68b58e96b6e4cd0fc08eb2b1"
+SRCREV_glibc ?= "0e1ef6779a90bc0f8a05bc367796df2793deecaa"
 SRCREV_localedef ?= "e0eca29583b9e0f62645c4316ced93cf4e4e26e1"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
meta/recipes-core/glibc/glibc/0024-CVE-2023-4527.patch deleted +0 -219

219 lines not on this page · raw message

meta/recipes-core/glibc/glibc_2.38.bb +0 -1
index 237458d066..32ccb888f0 100644
@@ -51,7 +51,6 @@ SRC_URI =  "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \
            file://0021-fix-create-thread-failed-in-unprivileged-process-BZ-.patch \
            file://0022-Avoid-hardcoded-build-time-paths-in-the-output-binar.patch \
            file://0023-aarch64-configure-Pass-mcpu-along-with-march-to-dete.patch \
-           file://0024-CVE-2023-4527.patch \
 "
 S = "${WORKDIR}/git"
 B = "${WORKDIR}/build-${TARGET_SYS}"
Signature · 1 line
2.39.0
#1 lore raw

Regression testing is done and below are the test results.

Before glibc update
Summary of test results:
213 FAIL
4805 PASS
16 XFAIL
4 XPASS
218 UNSUPPORTED

After glibc update
Summary of test results:
216 FAIL
4805 PASS
16 XFAIL
4 XPASS
218 UNSUPPORTED

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
FAIL: nss/tst-nss-gai-hv2-canonname
PASS: resolv/tst-resolv-noaaaa-vc
And below are new failures
FAIL: nptl/tst-thread-affinity-sched
FAIL: malloc/tst-malloc_info-malloc-check

#2 lore raw
Quoted 18 lines · Deepthi.Hemraj via lists.openembedded.org

Regression testing is done and below are the test results.

Before glibc update
Summary of test results:
213 FAIL
4805 PASS
16 XFAIL
4 XPASS
218 UNSUPPORTED

After glibc update
Summary of test results:
216 FAIL
4805 PASS
16 XFAIL
4 XPASS
218 UNSUPPORTED

Quoted 1 line

These are the newly added test cases

Thanks for the update, summary and initial analysis.

Quoted 2 lines

PASS: io/tst-fcntl-lock-lfs
FAIL: nss/tst-nss-gai-hv2-canonname

It's a little odd that a new test case is failing.

Is this reproducible?

Is there a bug reported upstream or discussed on an email list?

Quoted 4 lines

PASS: resolv/tst-resolv-noaaaa-vc
And below are new failures
FAIL: nptl/tst-thread-affinity-sched
FAIL: malloc/tst-malloc_info-malloc-check

Are these reproducible?

Is there a bug reported upstream?

Please do some additional analysis of the failures including whether they only happen in a bitbake build and report back here so we can decide how to proceed.

Thanks again Deepthi,

../Randy

Quoted 9 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188623):https://lists.openembedded.org/g/openembedded-core/message/188623 Mute This Topic:https://lists.openembedded.org/mt/101727838/3616765
Group Owner:[email protected] Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Signature · 2 lines
# Randy MacLeod
# Wind River Linux
#3 lore raw
In reply to [email protected]
Quoted 18 lines · Deepthi via lists.openembedded.org

From: Deepthi Hemraj <[email protected]>

Below commits on glibc-2.38 stable branch are updated.
0e1ef6779a (HEAD -> release/2.38/master, origin/release/2.38/master) manual/jobs.texi: Add missing @item EPERM for getpgid d94461bb86 string: Fix tester build with fortify enable with gcc < 12
63250e9c57 iconv: restore verbosity with unrecognized encoding names (bug 30694)
00ae4f10b5 getaddrinfo: Fix use after free in getcanonname (CVE-2023-4806)
b25508dd77 CVE-2023-4527: Stack read overflow with large TCP responses in no-aaaa mode
89da8bc588 NEWS: Add the 2.38.1 bug list
d3ba6c1333 elf: Move l_init_called_next to old place of l_text_end in link map
750f19526a elf: Remove unused l_text_end field from struct link_map
a3189f66a5 elf: Always call destructors in reverse constructor order (bug 30785)
7ae211a01b elf: Do not run constructors for proxy objects
92201f16cb libio: Fix oversized __io_vtables
5bdef6f27c io: Fix record locking contants for powerpc64 with __USE_FILE_OFFSET64

0024-CVE-2023-4527.patch is dropped

Quoted 7 lines
---
 meta/recipes-core/glibc/glibc-version.inc     |   2 +-
 .../glibc/glibc/0024-CVE-2023-4527.patch      | 219 ------------------
 meta/recipes-core/glibc/glibc_2.38.bb         |   1 -
 3 files changed, 1 insertion(+), 221 deletions(-)
 delete mode 100644 meta/recipes-core/glibc/glibc/0024-CVE-2023-4527.patch

I suspect that as well we deleting the patch, you need to add something like:

CVE_STATUS[CVE-2023-4527] = "fixed-version: Fixed in stable branch updates"

otherwise we'll see CVEs reported against this again?

There may be other CVEs which need adding too?

Cheers,

Richard

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 28 lines · Richard Purdie via lists.openembedded.org
Quoted 18 lines · Deepthi via lists.openembedded.org

From: Deepthi Hemraj <[email protected]>

Below commits on glibc-2.38 stable branch are updated.
0e1ef6779a (HEAD -> release/2.38/master, origin/release/2.38/master) manual/jobs.texi: Add missing @item EPERM for getpgid d94461bb86 string: Fix tester build with fortify enable with gcc < 12
63250e9c57 iconv: restore verbosity with unrecognized encoding names (bug 30694)
00ae4f10b5 getaddrinfo: Fix use after free in getcanonname (CVE-2023-4806)
b25508dd77 CVE-2023-4527: Stack read overflow with large TCP responses in no-aaaa mode
89da8bc588 NEWS: Add the 2.38.1 bug list
d3ba6c1333 elf: Move l_init_called_next to old place of l_text_end in link map
750f19526a elf: Remove unused l_text_end field from struct link_map
a3189f66a5 elf: Always call destructors in reverse constructor order (bug 30785)
7ae211a01b elf: Do not run constructors for proxy objects
92201f16cb libio: Fix oversized __io_vtables
5bdef6f27c io: Fix record locking contants for powerpc64 with __USE_FILE_OFFSET64

0024-CVE-2023-4527.patch is dropped

Quoted 7 lines
---
 meta/recipes-core/glibc/glibc-version.inc     |   2 +-
 .../glibc/glibc/0024-CVE-2023-4527.patch      | 219 ------------------
 meta/recipes-core/glibc/glibc_2.38.bb         |   1 -
 3 files changed, 1 insertion(+), 221 deletions(-)
 delete mode 100644 meta/recipes-core/glibc/glibc/0024-CVE-2023-4527.patch
Quoted 8 lines

I suspect that as well we deleting the patch, you need to add something like:

CVE_STATUS[CVE-2023-4527] = "fixed-version: Fixed in stable branch updates"

otherwise we'll see CVEs reported against this again?

There may be other CVEs which need adding too?

Since there appears to be a serious glibc issue we need to patch, I've gone ahead and added an update on top of this patch to pull in the new urgent pieces and set the CVE_STATUS accordingly. Please follow up with an additional patch for any other CVE_STATUS pieces I didn't cover.

Cheers,

Richard