Skip to content

Return linux-ptl to 7.1.11 with security backports - #420

Closed
spencerbull wants to merge 1 commit into
masterfrom
linux-ptl-7.1.11-security-backports
Closed

spencerbull wants to merge 1 commit into
masterfrom
linux-ptl-7.1.11-security-backports

Conversation

@spencerbull

Copy link
Copy Markdown
Contributor

Return linux-ptl to 7.1.11 to avoid the reported Xe regressions on 7.2, using the supplied build recipe and configuration already running on the maintainer's machine.

Retain all three Panther Lake display fixes: rebase the Panel Replay ALPM patches to 7.1, including the XPS 16 quirk, and keep the OLED DisplayID VRR patch unchanged. Backport the upstream TCP-AO use-after-free fix (CVE-2026-80850) and VXLAN FDB flush fix (CVE-2026-80838); both are needed on this 7.1.11 base.

Set epoch=1 so existing 7.2.x installations receive 1:7.1.11.arch1-1 through normal upgrades. The kernel release stays 7.1.11-arch1-1-ptl; the source, patch set, and input configuration match the supplied installed build. The package remains opted out of automatic builds.

Built both split packages with bin/build --package linux-ptl on a disposable Proxmox VM. Verified the normal local-repository upgrade from 7.2.4, boot into 7.1.11, clean package integrity, an external module built/loaded against the headers, 48 TCP-AO assertions, and VXLAN FDB tests. The fresh Xe module has identical code/data/relocations to the installed build; the epoch, build metadata/signing key, and Rust/bindgen-generated artifacts differ. Physical Panther Lake display behavior was not exercised in the VM.

Independent Codex XHigh source review found no substantive defects.

🤖 Generated by GPT-6 in Codex. Reviewed by Codex XHigh.

Keep the Panther Lake display patches on the 7.1 base to avoid the reported Xe regressions in 7.2. Backport the TCP-AO and VXLAN fixes for CVE-2026-80850 and CVE-2026-80838, and use epoch 1 so existing 7.2 installations receive the package as an upgrade.
@spencerbull
spencerbull marked this pull request as draft September 13, 2026 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant