Skip to content
Threat Brief

← All advisories

CVE-2026-99788

Severity unknownNo known exploitationFix available

ACPI: CPPC: Validate FFH register fields before hardware access

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 5% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Validate FFH register fields before hardware access The x86 CPPC FFH accessors construct masks and shift values using the firmware's Bit Width and Bit Offset without checking that the field fits in an MSR. A zero-width field or a field extending beyond bit 63 can therefore cause an invalid shift. The safe MSR accessors only handle an access fault, not invalid field arithmetic after a successful read. Also, the 64-bit GAS address is implicitly narrowed to the 32-bit MSR number. A descriptor with nonzero upper address bits can access a different MSR from the one described by firmware. The arm64 AMU counter readers have the same unchecked field arithmetic. Validate the field bounds before reading a counter, including both descriptors in the paired counter path. Dispatch FFH accesses before decoding the GAS Access Size in the common read and write paths. Otherwise, a large access_width can trigger an invalid shift in GET_BIT_WIDTH() before the architecture validates its register. That field has architecture-specific FFH semantics and is not needed by the generic memory/port accessor on this path. Validate x86 MSR addresses and share the field-bounds checks between related accessors within each architecture.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom a6cbcdd5ab5f242d49f511127f0a601b71be2cc4 before 353c0cb4375c57d282449cf87e8e405c2e8bc8ed353c0cb4375c57d282449cf87e8e405c2e8bc8edCVE Program
LinuxLinuxfrom a6cbcdd5ab5f242d49f511127f0a601b71be2cc4 before 4f6a4864308b57cf7aa38ddd07cf4ddcecfbcc414f6a4864308b57cf7aa38ddd07cf4ddcecfbcc41CVE Program
LinuxLinuxfrom a6cbcdd5ab5f242d49f511127f0a601b71be2cc4 before 6b016c5c96448c0a5f09328d37f66562d154a5e56b016c5c96448c0a5f09328d37f66562d154a5e5CVE Program
LinuxLinuxfrom a6cbcdd5ab5f242d49f511127f0a601b71be2cc4 before dd2322d548cc1b424da6d07e69eeab7543020106dd2322d548cc1b424da6d07e69eeab7543020106CVE Program
LinuxLinux4.9Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.9Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references