PoC Monitor
← All CVEs
CVE-2026-89436published 11 Sep 2026 19:43 UTCData: JSON · API

Linux

platform/x86: panasonic-laptop: Fix sentinel write past pcc->sinf[]

In the Linux kernel, the following vulnerability has been resolved: platform/x86: panasonic-laptop: Fix sentinel write past pcc->sinf[] acpi_pcc_retrieve_biosdata() rejects SINF packages only when pcc->num_sifr is strictly less than hkey->package.count, then unconditionally writes a trailing sentinel at pcc->sinf[hkey->package.count]. But pcc->sinf[] is allocated with exactly pcc->num_sifr elements (valid indices 0..num_sifr-1), so that write needs num_sifr strictly greater than package.count to stay in bounds -- num_sifr == package.count passes the existing check but still overflows by one element. This is exactly the case probe()'s existing num_sifr++ workaround ("Some DSDT-s have an off-by-one bug where the SINF package count is one higher than the SQTY reported value") is written to accommodate: when a DSDT's SINF package count equals SQTY+1, the workaround makes num_sifr equal to package.count, which is precisely the boundary that overflows here. Found via UBSan (array-index-out-of-bounds) on hardware where HKEY.SQTY returns 37 and HKEY.SINF()'s package has 38 elements: num_sifr becomes 38 after the += 1 workaround, the loop correctly fills indices 0..37, and the sentinel write then targets index 38, one past the end -- a silent 4-byte heap overflow on kernels without CONFIG_UBSAN. Tightening the rejection check to num_sifr <= package.count would avoid the overflow but breaks probe() entirely on exactly this hardware, since num_sifr == package.count is the case the off-by-one workaround exists to support. Nothing else in the driver reads this sentinel value back, so simply skip the write when there is no room for it instead.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= a3d0dbd18ce908292607bb6cf37c978ece8a33d4, < a93df956ee4d903735b6d395362c839cb1dc07e3
  • >= a3d0dbd18ce908292607bb6cf37c978ece8a33d4, < 329f10d8be193bf36af124e00b9dd6644cd71724

Fixed in a93df956ee4d903735b6d395362c839cb1dc07e3, 329f10d8be193bf36af124e00b9dd6644cd71724

Linux Linux
  • 7.2

Fixed in 0, 7.2.4, 7.3

Mitigation

Upgrade Linux to a93df956ee4d903735b6d395362c839cb1dc07e3 or 329f10d8be193bf36af124e00b9dd6644cd71724 or later.

Upgrade Linux to 0 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.