CVE-2026-99248 linux linux
linux linux: no CVSS score yet. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
On this page
In the Linux kernel, the following vulnerability has been resolved:
i2c: xiic: restore non-managed runtime PM to fix clk WARN flood
The devres conversion replaced manual pm_runtime_enable()/disable() with
devm_pm_runtime_set_active_enabled() and dropped the remove-time runtime
PM teardown. The managed release tears runtime PM down in the wrong
order: it calls pm_runtime_dont_use_autosuspend() before
pm_runtime_disable(), i.e. while runtime PM is still enabled, and devres
is LIFO so the devm_clk_get_enabled() release runs afterwards.
At remove(), pm_runtime_put_sync() leaves the device active with the
autosuspend timer armed. Clearing use_autosuspend then makes rpm_idle()
suspend immediately, and xiic_i2c_runtime_suspend() clk_disable()s the
clock. The later devm_clk_get_enabled() release clk_disable_unprepare()s
the already-disabled clock, so clk_core_disable() WARNs ("clkN already
disabled") on every teardown.
Drop the managed helper and restore the non-managed runtime PM setup and
teardown, so runtime PM is enabled once in probe and disabled once in
remove and the clock enable count stays balanced.
Order the remove teardown so runtime PM is disabled before the usage
count is dropped: pm_runtime_disable() followed by pm_runtime_put_noidle()
instead of pm_runtime_put_sync(). Dropping the count first with autosuspend
still enabled arms the autosuspend timer, and a preemption before
pm_runtime_disable() lets it expire, suspend the device and clk_disable()
the clock, which the devm release then disables again - the same WARN.
Restore the non-managed IRQ request as well. The probe error paths now
unwind runtime PM by hand via goto, and a devm-registered handler is only
freed later during devres unwind, so it would stay live across the manual
teardown (and across any future failing step added after it). Request the
IRQ with request_threaded_irq() and free it explicitly in the probe error
path and in remove. The probe error path also clears use_autosuspend, to
match the teardown in remove().
- EPSS
- 0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 7.2.13
- Linux Linux: fixed in 7.3
- Debian, Ubuntu: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-99248 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99248?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99248?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99248 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 7.1 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 7.2 | 7.2.13 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.2.13-1 | DEBIAN-CVE-2026-99248 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99248 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99248 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99248 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-99248 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 23 more | no fix listed | UBUNTU-CVE-2026-99248 |
| Ubuntu | 26.10 | linux | 7.3.0-10.10 | UBUNTU-CVE-2026-99248 |
| Ubuntu | 26.10 | linux-aws, linux-gcp, linux-azure and 2 more | 7.3.0-1004.4 | UBUNTU-CVE-2026-99248 |
| Ubuntu | 26.10 | linux-azure-fde | 7.3.0-1004.5 | UBUNTU-CVE-2026-99248 |
| Ubuntu | 26.10 | linux-riscv, linux-realtime | 7.3.0-10.10.1 | UBUNTU-CVE-2026-99248 |
| Ubuntu | Pro:Realtime:24.04:LTS | linux-realtime-6.14, linux-realtime-6.17 | no fix listed | UBUNTU-CVE-2026-99248 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.