bind: Upgrade 9.18.44 -> 9.18.49
PATCH v2 1/1 bind: Upgrade 9.18.44 -> 9.18.49
From: Ashishkumar Parmar <[email protected]>
This upgrade fixes CVE-2026-1519, CVE-2026-3039, CVE-2026-3592, CVE-2026-5946 and CVE-2026-5950.
Changelog
=========
https://downloads.isc.org/isc/bind9/9.18.49/doc/arm/html/notes.html
---
.../bind/{bind_9.18.44.bb => bind_9.18.49.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/bind/{bind_9.18.44.bb => bind_9.18.49.bb} (97%)meta/recipes-connectivity/bind/bind_9.18.49.bb renamed from meta/recipes-connectivity/bind/bind_9.18.44.bb +1 -1
@@ -20,7 +20,7 @@ SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ file://0001-avoid-start-failure-with-bind-user.patch \ " -SRC_URI[sha256sum] = "81f5035a25c576af1a93f0061cf70bde6d00a0c7bd1274abf73f5b5389a6f82d" +SRC_URI[sha256sum] = "c43ce4548ebed788cd9df63658a7de105ceafba43fcd63fa352b1093e525cd24" UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/" # follow the ESV versions divisible by 2
Signature · 1 line
2.35.6
Quoted 7 lines · On Tue Jun 30, 2026 at 8:04 AM CEST, Ashishkumar Parmar X (asparmar - E…
From: Ashishkumar Parmar <[email protected]>
This upgrade fixes CVE-2026-1519, CVE-2026-3039, CVE-2026-3592, CVE-2026-5946 and CVE-2026-5950.
Changelog
=========
https://downloads.isc.org/isc/bind9/9.18.49/doc/arm/html/notes.html
That changelog contains:
| Notes for BIND 9.18.45 | Feature Changes | Update requirements for system test suite. | Python 3.10 or newer is now required for running the system test | suite. The required Python packages and their version requirements | are now tracked in the file bin/tests/system/requirements.txt. [GL | #5690] [GL #5614]
Feature changes are not usually acceptable for stable. Can you justify why this is the case here?
Thanks!
Quoted 23 lines
Signed-off-by Ashishkumar Parmar <[email protected]>--- .../bind/{bind_9.18.44.bb => bind_9.18.49.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-connectivity/bind/{bind_9.18.44.bb => bind_9.18.49.bb} (97%)meta/recipes-connectivity/bind/bind_9.18.49.bb renamed from meta/recipes-connectivity/bind/bind_9.18.44.bb +1
-1@@ -20,7 +20,7 @@ SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ file://0001-avoid-start-failure-with-bind-user.patch \ " -SRC_URI[sha256sum] = "81f5035a25c576af1a93f0061cf70bde6d00a0c7bd1274abf73f5b5389a6f82d" +SRC_URI[sha256sum] = "c43ce4548ebed788cd9df63658a7de105ceafba43fcd63fa352b1093e525cd24" UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/" # follow the ESV versions divisible by 2
Signature · 2 lines
Yoann Congal Smile ECS
Thanks, Yoann.
Yes, feature changes are usually not something we should take in stable.
For this BIND work, I first submitted the individual CVE backport patches for scarthgap:
- CVE-2026-1519:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-5950:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-3592:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-3039:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-5946:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
During review, the feedback was that BIND is one of the rare projects where the upstream stable branch matches OE stable policy, and that upgrading along the 9.18 branch would be preferable to carrying a large CVE backport patch stack. That is why I superseded the backport series and sent the 9.18.44 -> 9.18.49 upgrade instead:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
For the specific 9.18.45 changelog item you pointed out, the change is limited to ISC's upstream system test suite. It raises the Python requirement for running bin/tests/system and tracks those test-suite Python dependencies in bin/tests/system/requirements.txt.
OE-Core's bind recipe does not enable or package that upstream system test suite and does not inherit ptest, so this change is not part of the target build, installed packages, runtime dependencies, or runtime behavior.
So the reason for the upgrade is that it follows the earlier review direction to use the BIND 9.18 stable branch, while this particular feature change is test-suite-only and not target-visible in OE-Core.
Regards,
Ashish
________________________________
From: Yoann Congal <[email protected]>
Sent: 07 July 2026 15:49
To: Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco) <[email protected]>; [email protected] <[email protected]>
Cc: xe-linux-external (Internal Group) <[email protected]>
Subject: Re: [OE-core][scarthgap][PATCH v2] bind: Upgrade 9.18.44 -> 9.18.49
Quoted 7 lines · On Tue Jun 30, 2026 at 8:04 AM CEST, Ashishkumar Parmar X (asparmar - E…
From: Ashishkumar Parmar <[email protected]>
This upgrade fixes CVE-2026-1519, CVE-2026-3039, CVE-2026-3592, CVE-2026-5946 and CVE-2026-5950.
Changelog
=========
https://downloads.isc.org/isc/bind9/9.18.49/doc/arm/html/notes.html
That changelog contains:
| Notes for BIND 9.18.45 | Feature Changes | Update requirements for system test suite. | Python 3.10 or newer is now required for running the system test | suite. The required Python packages and their version requirements | are now tracked in the file bin/tests/system/requirements.txt. [GL | #5690] [GL #5614]
Feature changes are not usually acceptable for stable. Can you justify why this is the case here?
Thanks!
Quoted 15 lines
Signed-off-by Ashishkumar Parmar <[email protected]>--- .../bind/{bind_9.18.44.bb => bind_9.18.49.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-connectivity/bind/{bind_9.18.44.bb => bind_9.18.49.bb} (97%)meta/recipes-connectivity/bind/bind_9.18.49.bb renamed from meta/recipes-connectivity/bind/bind_9.18.44.bb +0
-0
meta/recipes-connectivity/bind/bind_9.18.49.bb SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ · line 26
Quoted 8 lines
meta/recipes-connectivity/bind/bind_9.18.49.bb renamed from meta/recipes-connectivity/bind/bind_9.18.44.bb +1
-1@@ -20,7 +20,7 @@ SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ file://0001-avoid-start-failure-with-bind-user.patch \ " -SRC_URI[sha256sum] = "81f5035a25c576af1a93f0061cf70bde6d00a0c7bd1274abf73f5b5389a6f82d" +SRC_URI[sha256sum] = "c43ce4548ebed788cd9df63658a7de105ceafba43fcd63fa352b1093e525cd24" UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/" # follow the ESV versions divisible by 2
--
Yoann Congal
Smile ECS
Hello,
Quoted 17 lines · On Tue Jul 7, 2026 at 3:24 PM CEST, Ashishkumar Parmar -X (asparmar - E…
Thanks, Yoann.
Yes, feature changes are usually not something we should take in stable.
For this BIND work, I first submitted the individual CVE backport patches for scarthgap:
- CVE-2026-1519:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-5950:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-3592:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-3039:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-5946:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
Quoted 8 lines
During review, the feedback was that BIND is one of the rare projects where the upstream stable branch matches OE stable policy, and that upgrading along the 9.18 branch would be preferable to carrying a large CVE backport patch stack. That is why I superseded the backport series and sent the 9.18.44 -> 9.18.49
upgrade instead:https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
Sorry, I totally forgot that I was the one suggesting the upgrade.
Quoted 5 lines
For the specific 9.18.45 changelog item you pointed out, the change is limited to ISC's upstream system test suite. It raises the Python requirement for running
bin/tests/systemand tracks those test-suite Python dependencies inbin/tests/system/requirements.txt.
Quoted 8 lines
OE-Core's
bindrecipe does not enable or package that upstream system test suite and does not inheritptest, so this change is not part of the target build, installed packages, runtime dependencies, or runtime behavior.So the reason for the upgrade is that it follows the earlier review direction to use the BIND 9.18 stable branch, while this particular feature change is test-suite-only and not target-visible in OE-Core.
I agree with proceeding with the upgrade.
Can you put a shorter explanation of the above in your commit message to help future reviewer?
Thanks!
Quoted 61 lines
Regards,
Ashish
________________________________
From: Yoann Congal <[email protected]>
Sent: 07 July 2026 15:49
To: Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco) <[email protected]>; [email protected] <[email protected]>
Cc: xe-linux-external (Internal Group) <[email protected]>
Subject: Re: [OE-core][scarthgap][PATCH v2] bind: Upgrade 9.18.44 -> 9.18.49Quoted 7 lines · On Tue Jun 30, 2026 at 8:04 AM CEST, Ashishkumar Parmar X (asparmar - E…
From: Ashishkumar Parmar <[email protected]>
This upgrade fixes CVE-2026-1519, CVE-2026-3039, CVE-2026-3592, CVE-2026-5946 and CVE-2026-5950.
Changelog
=========
https://downloads.isc.org/isc/bind9/9.18.49/doc/arm/html/notes.htmlThat changelog contains:
| Notes for BIND 9.18.45 | Feature Changes | Update requirements for system test suite. | Python 3.10 or newer is now required for running the system test | suite. The required Python packages and their version requirements | are now tracked in the file bin/tests/system/requirements.txt. [GL | #5690] [GL #5614]Feature changes are not usually acceptable for stable. Can you justify why this is the case here?
Thanks!
Quoted 15 lines
Signed-off-by Ashishkumar Parmar <[email protected]>--- .../bind/{bind_9.18.44.bb => bind_9.18.49.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-connectivity/bind/{bind_9.18.44.bb => bind_9.18.49.bb} (97%)meta/recipes-connectivity/bind/bind_9.18.49.bb renamed from meta/recipes-connectivity/bind/bind_9.18.44.bb +0
-0meta/recipes-connectivity/bind/bind_9.18.49.bb SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ · line 26
Quoted 8 lines
meta/recipes-connectivity/bind/bind_9.18.49.bb renamed from meta/recipes-connectivity/bind/bind_9.18.44.bb +1
-1@@ -20,7 +20,7 @@ SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ file://0001-avoid-start-failure-with-bind-user.patch \ " -SRC_URI[sha256sum] = "81f5035a25c576af1a93f0061cf70bde6d00a0c7bd1274abf73f5b5389a6f82d" +SRC_URI[sha256sum] = "c43ce4548ebed788cd9df63658a7de105ceafba43fcd63fa352b1093e525cd24" UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/" # follow the ESV versions divisible by 2--
Yoann Congal
Smile ECS
Signature · 2 lines
Yoann Congal Smile ECS
Hi Yoann,
Thanks for the clarification.
I have sent the updated patch for this.
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
Regards,
Ashish
________________________________
From: Yoann Congal <[email protected]>
Sent: 07 July 2026 19:54
To: Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco) <[email protected]>; [email protected] <[email protected]>
Subject: Re: [OE-core][scarthgap][PATCH v2] bind: Upgrade 9.18.44 -> 9.18.49
Hello,
Quoted 17 lines · On Tue Jul 7, 2026 at 3:24 PM CEST, Ashishkumar Parmar -X (asparmar - E…
Thanks, Yoann.
Yes, feature changes are usually not something we should take in stable.
For this BIND work, I first submitted the individual CVE backport patches for scarthgap:
- CVE-2026-1519:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-5950:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-3592:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-3039:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
- CVE-2026-5946:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
Quoted 8 lines
During review, the feedback was that BIND is one of the rare projects where the upstream stable branch matches OE stable policy, and that upgrading along the 9.18 branch would be preferable to carrying a large CVE backport patch stack. That is why I superseded the backport series and sent the 9.18.44 -> 9.18.49
upgrade instead:https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/
Sorry, I totally forgot that I was the one suggesting the upgrade.
Quoted 5 lines
For the specific 9.18.45 changelog item you pointed out, the change is limited to ISC's upstream system test suite. It raises the Python requirement for running
bin/tests/systemand tracks those test-suite Python dependencies inbin/tests/system/requirements.txt.
Quoted 8 lines
OE-Core's
bindrecipe does not enable or package that upstream system test suite and does not inheritptest, so this change is not part of the target build, installed packages, runtime dependencies, or runtime behavior.So the reason for the upgrade is that it follows the earlier review direction to use the BIND 9.18 stable branch, while this particular feature change is test-suite-only and not target-visible in OE-Core.
I agree with proceeding with the upgrade.
Can you put a shorter explanation of the above in your commit message to help future reviewer?
Thanks!
Quoted 54 lines
Regards,
Ashish
________________________________
From: Yoann Congal <[email protected]>
Sent: 07 July 2026 15:49
To: Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco) <[email protected]>; [email protected] <[email protected]>
Cc: xe-linux-external (Internal Group) <[email protected]>
Subject: Re: [OE-core][scarthgap][PATCH v2] bind: Upgrade 9.18.44 -> 9.18.49Quoted 7 lines · On Tue Jun 30, 2026 at 8:04 AM CEST, Ashishkumar Parmar X (asparmar - E…
From: Ashishkumar Parmar <[email protected]>
This upgrade fixes CVE-2026-1519, CVE-2026-3039, CVE-2026-3592, CVE-2026-5946 and CVE-2026-5950.
Changelog
=========
https://downloads.isc.org/isc/bind9/9.18.49/doc/arm/html/notes.htmlThat changelog contains:
| Notes for BIND 9.18.45 | Feature Changes | Update requirements for system test suite. | Python 3.10 or newer is now required for running the system test | suite. The required Python packages and their version requirements | are now tracked in the file bin/tests/system/requirements.txt. [GL | #5690] [GL #5614]Feature changes are not usually acceptable for stable. Can you justify why this is the case here?
Thanks!
Quoted 21 lines
Signed-off-by Ashishkumar Parmar <[email protected]>--- .../bind/{bind_9.18.44.bb => bind_9.18.49.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-connectivity/bind/{bind_9.18.44.bb => bind_9.18.49.bb} (97%)meta/recipes-connectivity/bind/bind_9.18.49.bb renamed from meta/recipes-connectivity/bind/bind_9.18.44.bb +1
-1@@ -20,7 +20,7 @@ SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ file://0001-avoid-start-failure-with-bind-user.patch \ " -SRC_URI[sha256sum] = "81f5035a25c576af1a93f0061cf70bde6d00a0c7bd1274abf73f5b5389a6f82d" +SRC_URI[sha256sum] = "c43ce4548ebed788cd9df63658a7de105ceafba43fcd63fa352b1093e525cd24"
Quoted 7 lines
meta/recipes-connectivity/bind/bind_9.18.49.bb SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ · line 26
Quoted 2 lines
meta/recipes-connectivity/bind/bind_9.18.49.bb renamed from meta/recipes-connectivity/bind/bind_9.18.44.bb +0
-0UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/" # follow the ESV versions divisible by 2--
Yoann Congal
Smile ECS
--
Yoann Congal
Smile ECS