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

No public exploit for CVE-2026-99140 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.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix hist trigger timestamps for buffered events Syzkaller…

CVE-2026-99140

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix hist trigger timestamps for buffered events Syzkaller triggered a WARNONONCE(!nest) warning: WARNING: kernel/trace/ringbuffer.c:821 at ringbuffereventtimestamp Call trace: ringbuffereventtimestamp histfieldtimestamp histfncall eventhisttrigger eventtriggerscall eventtriggertestdiscard traceeventbuffercommit dotraceeventraweventschedswitch traceeventraweventschedswitch The warning is probabilistically reproducible and is related to syzkaller executing the following commands: echo 'prevpid == 999999' > events/sched/schedswitch/filter echo 'hist:keys=commontimestamp' > events/sched/schedswitch/trigger The specific triggering process is as follows: CPU 0 CPU 1 (context switching) (echo 'hist:keys=commontimestamp' > \ events/sched/schedswitch/trigger) dotraceeventrawevent##call traceeventbufferlockreserve if (!tr->nofilterbufferingref && tracefile->flags & EVENTFILEFLFILTERED) return entry; // return directly eventhisttriggerparse histregistertrigger tracingsetfilterbuffering(file->tr, true); tr->nofilterbufferingref++; tracebufferlockreserve rbstartcommit localinc(&cpubuffer->committing); // skipped and…

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: 28 October 2026
Last updated: 30 October 2026
Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

At the source

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 8 + 6? *

Query this programmatically

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

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