From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [wrynose][PATCH 0/3] acl: Security fixes To: openembedded-core@lists.openembedded.org From: "Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)" X-Originating-Location: Mumbai, Maharashtra, IN (151.186.177.83) X-Originating-Platform: Windows Edge 157 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Tue, 17 Nov 2026 04:34:03 -0800 References: <20261104055335.2080900-1-dkelaiya@cisco.com> In-Reply-To: Message-ID: <882014.1794918843277220981@lists.openembedded.org> Content-Type: multipart/alternative; boundary="iRnlYpYe1fJz5fdiGdh4" List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by lin-tor-korg-lkml-alma10-1 with HTTPS for ; Tue, 17 Nov 2026 12:34:03 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/250442 --iRnlYpYe1fJz5fdiGdh4 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Yoann, Thanks for reviewing this. I haven't identified any definite breakage specific to upgrading to ACL 2.4.0. My original choice followed the usual stable-branch backport approach. I agree that this series already introduces substantial changes, including the new APIs, compatibility helpers and directory walker. Keeping the 2.3.2 version therefore does not necessarily provide a lower-risk result. Upstream also recommends updating these packages even on older distributions: https://www.openwall.com/lists/oss-security/2026/06/29/1#:~:text=3DYou%20pr= obably%20want,org/projects/acl I'm happy to evaluate the 2.4.0 upgrade. That would give us a firmer basis for considering an upgrade exception for Wrynose. Regards, Darsh On Sun, Nov 15, 2026 at 05:39 AM, Yoann Congal wrote: >=20 > On Wed Nov 4, 2026 at 6:53 AM CET, Darsh Kelaiya -X (dkelaiya - E > INFOCHIPS PRIVATE LIMITED at Cisco) via openembedded-core wrote: >=20 >> From: Darsh Kelaiya >>=20 >> Backport the upstream fixes for CVE-2026-54369 and CVE-2026-54370 to >> ACL 2.3.2. >>=20 >> CVE-2026-54369 adds descriptor-relative ACL APIs so callers can control >> symlink traversal. CVE-2026-54370 uses those APIs to harden getfacl, >> setfacl, setfacl --restore and chacl against path replacement races and >> unsafe symlink traversal. >>=20 >> Retain ACL 2.3.2 on the stable Wrynose branch and backport the security >> fixes with the required _at APIs and helper dependencies. This follows >> OE-Core's focus on security and bug fixes for stable branches [1], >> avoiding a general recipe upgrade to ACL 2.4.0. Existing pathname API >> behavior is preserved. >>=20 >> The new public acl_*_at declarations conflict with private helpers >> using the same names in GNU tar 1.35. Patch 1 backports the upstream >> tar rename before patches 2 and 3 introduce and consume >> the new ACL APIs. >>=20 >> [1] https://docs.yoctoproject.org/6.0/ref-manual/release-process.html#st= able-release-process >>=20 >>=20 >> Darsh Kelaiya (3): >> tar: avoid name conflicts with new libacl APIs >> acl: fix CVE-2026-54369 >> acl: fix CVE-2026-54370 >>=20 >> .../tar/tar/Avoid-acl_-prefix-for-functions.patch | 103 ++ >> meta/recipes-extended/tar/tar_1.35.bb | 1 + >> .../attr/acl/CVE-2026-54369-dependent_p1.patch | 69 ++ >> .../attr/acl/CVE-2026-54369-dependent_p2.patch | 200 ++++ >> .../attr/acl/CVE-2026-54369-dependent_p3.patch | 712 +++++++++++++ >> meta/recipes-support/attr/acl/CVE-2026-54369_p1.patch | 719 ++++++++++++= + >> meta/recipes-support/attr/acl/CVE-2026-54369_p2.patch | 957 >> ++++++++++++++++++ >> meta/recipes-support/attr/acl/CVE-2026-54369_p3.patch | 109 ++ >> .../attr/acl/CVE-2026-54370-dependent_p1.patch | 168 +++ >> .../attr/acl/CVE-2026-54370-dependent_p2.patch | 761 ++++++++++++++ >> .../attr/acl/CVE-2026-54370-dependent_p3.patch | 439 ++++++++ >> .../attr/acl/CVE-2026-54370-dependent_p4.patch | 140 +++ >> meta/recipes-support/attr/acl/CVE-2026-54370_p1.patch | 299 ++++++ >> meta/recipes-support/attr/acl/CVE-2026-54370_p2.patch | 403 ++++++++ >> meta/recipes-support/attr/acl/CVE-2026-54370_p3.patch | 603 +++++++++++ >> meta/recipes-support/attr/acl/CVE-2026-54370_p4.patch | 213 ++++ >> meta/recipes-support/attr/acl_2.3.2.bb | 14 + >> 17 files changed, 5910 insertions(+) >> create mode 100644 >> meta/recipes-extended/tar/tar/Avoid-acl_-prefix-for-functions.patch >> create mode 100644 >> meta/recipes-support/attr/acl/CVE-2026-54369-dependent_p1.patch >> create mode 100644 >> meta/recipes-support/attr/acl/CVE-2026-54369-dependent_p2.patch >> create mode 100644 >> meta/recipes-support/attr/acl/CVE-2026-54369-dependent_p3.patch >> create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54369_p1.patch >> create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54369_p2.patch >> create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54369_p3.patch >> create mode 100644 >> meta/recipes-support/attr/acl/CVE-2026-54370-dependent_p1.patch >> create mode 100644 >> meta/recipes-support/attr/acl/CVE-2026-54370-dependent_p2.patch >> create mode 100644 >> meta/recipes-support/attr/acl/CVE-2026-54370-dependent_p3.patch >> create mode 100644 >> meta/recipes-support/attr/acl/CVE-2026-54370-dependent_p4.patch >> create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54370_p1.patch >> create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54370_p2.patch >> create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54370_p3.patch >> create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54370_p4.patch >=20 > Hello, >=20 > This is quite a big series ("5910 insertions(+)"). Looking at it, I think > this might be just backporting most of the risky parts of the 2.4.0 > upgrade, but then, we might just be better off simply upgrading to > 2.4.0. Do you have thoughts about that? Are there definite breakage on a > potential 2.4.0 upgrade? >=20 > Obviously, a 2.4.0 upgrade would need serious thoughts/discussion but > this might be the way forward. >=20 > Regards, > -- > Yoann Congal > Smile ECS --iRnlYpYe1fJz5fdiGdh4 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Hi Yoann,

Thanks for reviewing this. I haven't identified a= ny definite breakage
specific to upgrading to ACL 2.4.0. My original c= hoice followed the
usual stable-branch backport approach.

I= agree that this series already introduces substantial changes,
includ= ing the new APIs, compatibility helpers and directory walker.
Keeping = the 2.3.2 version therefore does not necessarily provide a
lower-risk = result.

Upstream also recommends updating these packages even on= older
distributions:

https://www.openwall.com/lists/oss= -security/2026/06/29/1#:~:text=3DYou%20probably%20want,org/projects/acl=  

I'm happy to evaluate the 2.4.0 upgrade. That would give = us a firmer
basis for considering an upgrade exception for Wrynose.
Regards,
Darsh

On Sun, Nov 15, 2026 at 05:39 AM, Y= oann Congal wrote:
On Wed Nov 4, 2026 at 6:53 AM CET, Darsh Kelaiya -X (dkelaiya -= E INFOCHIPS PRIVATE LIMITED at Cisco) via openembedded-core wrote:
From: Darsh Kelaiya <dkelaiya@cisco.com>

Backp= ort the upstream fixes for CVE-2026-54369 and CVE-2026-54370 to
ACL 2.= 3.2.

CVE-2026-54369 adds descriptor-relative ACL APIs so callers= can control
symlink traversal. CVE-2026-54370 uses those APIs to hard= en getfacl,
setfacl, setfacl --restore and chacl against path replacem= ent races and
unsafe symlink traversal.

Retain ACL 2.3.2 on= the stable Wrynose branch and backport the security
fixes with the re= quired _at APIs and helper dependencies. This follows
OE-Core's focus = on security and bug fixes for stable branches [1],
avoiding a general = recipe upgrade to ACL 2.4.0. Existing pathname API
behavior is preserv= ed.

The new public acl_*_at declarations conflict with private h= elpers
using the same names in GNU tar 1.35. Patch 1 backports the ups= tream
tar rename before patches 2 and 3 introduce and consume
the= new ACL APIs.

[1] https://docs.yoctoproject.org/6.0/ref-manual/release-proces= s.html#stable-release-process

Darsh Kelaiya (3):
tar: a= void name conflicts with new libacl APIs
acl: fix CVE-2026-54369
= acl: fix CVE-2026-54370

.../tar/tar/Avoid-acl_-prefix-for-functi= ons.patch | 103 ++
meta/recipes-extended/tar/tar_1.35.bb | 1 +
..= ./attr/acl/CVE-2026-54369-dependent_p1.patch | 69 ++
.../attr/acl/CVE-= 2026-54369-dependent_p2.patch | 200 ++++
.../attr/acl/CVE-2026-54369-d= ependent_p3.patch | 712 +++++++++++++
meta/recipes-support/attr/acl/CV= E-2026-54369_p1.patch | 719 +++++++++++++
meta/recipes-support/attr/ac= l/CVE-2026-54369_p2.patch | 957 ++++++++++++++++++
meta/recipes-suppor= t/attr/acl/CVE-2026-54369_p3.patch | 109 ++
.../attr/acl/CVE-2026-5437= 0-dependent_p1.patch | 168 +++
.../attr/acl/CVE-2026-54370-dependent_p= 2.patch | 761 ++++++++++++++
.../attr/acl/CVE-2026-54370-dependent_p3.= patch | 439 ++++++++
.../attr/acl/CVE-2026-54370-dependent_p4.patch | = 140 +++
meta/recipes-support/attr/acl/CVE-2026-54370_p1.patch | 299 ++= ++++
meta/recipes-support/attr/acl/CVE-2026-54370_p2.patch | 403 +++++= +++
meta/recipes-support/attr/acl/CVE-2026-54370_p3.patch | 603 ++++++= +++++
meta/recipes-support/attr/acl/CVE-2026-54370_p4.patch | 213 ++++=
meta/recipes-support/attr/acl_2.3.2.bb | 14 +
17 files changed, = 5910 insertions(+)
create mode 100644 meta/recipes-extended/tar/tar/Av= oid-acl_-prefix-for-functions.patch
create mode 100644 meta/recipes-su= pport/attr/acl/CVE-2026-54369-dependent_p1.patch
create mode 100644 me= ta/recipes-support/attr/acl/CVE-2026-54369-dependent_p2.patch
create m= ode 100644 meta/recipes-support/attr/acl/CVE-2026-54369-dependent_p3.patch<= br />create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54369_p1.pat= ch
create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54369_p2.= patch
create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54369_= p3.patch
create mode 100644 meta/recipes-support/attr/acl/CVE-2026-543= 70-dependent_p1.patch
create mode 100644 meta/recipes-support/attr/acl= /CVE-2026-54370-dependent_p2.patch
create mode 100644 meta/recipes-sup= port/attr/acl/CVE-2026-54370-dependent_p3.patch
create mode 100644 met= a/recipes-support/attr/acl/CVE-2026-54370-dependent_p4.patch
create mo= de 100644 meta/recipes-support/attr/acl/CVE-2026-54370_p1.patch
create= mode 100644 meta/recipes-support/attr/acl/CVE-2026-54370_p2.patch
cre= ate mode 100644 meta/recipes-support/attr/acl/CVE-2026-54370_p3.patch
= create mode 100644 meta/recipes-support/attr/acl/CVE-2026-54370_p4.patch Hello,

This is quite a big series ("5910 insertions(+)"). Lookin= g at it, I think
this might be just backporting most of the risky part= s of the 2.4.0
upgrade, but then, we might just be better off simply u= pgrading to
2.4.0. Do you have thoughts about that? Are there definite= breakage on a
potential 2.4.0 upgrade?

Obviously, a 2.4.0 = upgrade would need serious thoughts/discussion but
this might be the w= ay forward.

Regards,
--
Yoann Congal
Smile ECS
--iRnlYpYe1fJz5fdiGdh4--