Is there a public exploit for CVE-2026-99248?

No public exploit for CVE-2026-99248 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

What does CVE-2026-99248 affect?

CVE-2026-99248 affects Linux Linux.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: i2c: xiic: restore non-managed runtime PM to fix clk WARN flood The…

CVE-2026-99248

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 pmruntimeenable()/disable() with devmpmruntimesetactiveenabled() and dropped the remove-time runtime PM teardown. The managed release tears runtime PM down in the wrong order: it calls pmruntimedontuseautosuspend() before pmruntimedisable(), i.e. while runtime PM is still enabled, and devres is LIFO so the devmclkgetenabled() release runs afterwards. At remove(), pmruntimeputsync() leaves the device active with the autosuspend timer armed. Clearing useautosuspend then makes rpmidle() suspend immediately, and xiici2cruntimesuspend() clkdisable()s the clock. The later devmclkgetenabled() release clkdisableunprepare()s the already-disabled clock, so clkcoredisable() 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: pmruntimedisable()…

Assessment

CVSS: Not yet scored
Severity: Unscored
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 3 November 2026
Last updated: 3 November 2026
Affected: Linux · Linux
Assigner: Linux

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 4 + 1? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99248