Skip to content

DLPX-100351 Ubuntu Security Notification for PCRE2 Vulnerabilities (USN-8974-1) - #426

Merged
david-mendez1 merged 1 commit into
releasefrom
dlpx/pr/david-mendez1/4ea9a48e-1833-4879-a818-89e824c2c834
Nov 9, 2026
Merged

david-mendez1 merged 1 commit into
releasefrom
dlpx/pr/david-mendez1/4ea9a48e-1833-4879-a818-89e824c2c834

Conversation

@david-mendez1

@david-mendez1 david-mendez1 commented Nov 8, 2026 •

Copy link
Copy Markdown

Jira: DLPX-100351 Ubuntu Security Notification for PCRE2 Vulnerabilities (USN-8974-1)

Problem

linux-pkg PR 425 pinned only libpcre2-8-0 at 10.42-4ubuntu2.2. libpcre2-dev (pulled in by the unpinned libselinux-dev) still resolves to the older build from the release mirror, and that build requires libpcre2-8-0 at exactly 10.42-4ubuntu2.1. The live-build 80-build-configuration hook then fails:

libpcre2-dev : Depends: libpcre2-8-0 (= 10.42-4ubuntu2.1) but 10.42-4ubuntu2.2 is to be installed
E: Unable to correct problems, you have held broken packages.

First seen in appliance-build-stage1/post-push #287358, failing :live-build:buildInternalDevKvm.

Solution

Add libpcre2-dev, libpcre2-16-0, libpcre2-32-0 and libpcre2-posix3 at 10.42-4ubuntu2.2 to packages/misc-debs/config.sh, so the whole pcre2 set moves together. libpcre2-dev depends on the other three at its own version, so all four are required.

The debs come from the develop apt mirror (noble-updates/noble-security), staged on the cve-package-check VM and uploaded to linux-pkg/misc-debs/ on Artifactory. Each entry is sha256-pinned.

Testing Done

  • Package set and dependencies confirmed on cve-package-check (develop build 2027.1.0.0-snapshot…post-push-4933, noble/amd64): libselinux1-dev depends on libpcre2-dev, which depends on -8-0, -16-0, -32-0 and -posix3; the changelog for 10.42-4ubuntu2.2 lists CVE-2026-103111 and CVE-2026-86145.
  • Checksums: each deb re-downloaded from Artifactory after upload; the sha256 matches the value pinned in config.sh.
  • shfmt -d and shellcheck -x on packages/misc-debs/config.sh: clean.
  • PASSED, expected to pass · PR head · appliance image build · appliance-build release pre-push #299, with misc-debs rebuilt from this branch. This is the step that failed before the fix.
  • PASSED, expected to pass · PR head · pre_checkin blackbox tests · blackbox-self-service #238534.
  • FAILED, not caused by this change · PR head · upgrade test · upgrade-testing #4814: the test environment failed before any upgrade ran (Windows test hosts never resolved in DNS). The same error occurred in the three earlier runs checked, #4810, #4812 and #4813, and the job has failed in each of its last 8 runs. No upgrade has been exercised against this change.
FAILED overall, only because of the upgrade test · PR head · appliance build + tests · ab-pre-push #15858

ab-pre-push build #15858: FAILURE (finished 2026-11-09 05:09 UTC)

Everything passed except upgrade-testing #4814, which failed on a DNS/environment error (below). The orchestrator reports FAILURE because it propagates that result.

Prior runs (1, same commit)

FAILED, expected to pass · ab-pre-push #15856: this run did not exercise the change. The stage0 job reused the prebuilt release/build-package/misc-debs/post-push/11 artifact instead of rebuilding misc-debs from this branch, so the new pins were never in the image, and appliance-build-stage1 » pre-push #67293 failed with the same libpcre2-dev … held broken packages error as the Problem section. Re-run as #15858 with -b misc-debs.

🤖 Generated with Claude Code

@david-mendez1
david-mendez1 force-pushed the dlpx/pr/david-mendez1/4ea9a48e-1833-4879-a818-89e824c2c834 branch from 759d63b to 8f03146 Compare November 8, 2026 19:14
@david-mendez1
david-mendez1 marked this pull request as ready for review November 8, 2026 19:21
@david-mendez1
david-mendez1 merged commit 12fab68 into release Nov 9, 2026
21 checks passed
@david-mendez1
david-mendez1 deleted the dlpx/pr/david-mendez1/4ea9a48e-1833-4879-a818-89e824c2c834 branch November 9, 2026 03:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants