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

No public exploit for CVE-2026-99282 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-99282 affect?

CVE-2026-99282 affects Linux Linux.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: net/sched: schteql: fix use-after-free on lower qdisc drop The issue:…

CVE-2026-99282

In the Linux kernel, the following vulnerability has been resolved: net/sched: schteql: fix use-after-free on lower qdisc drop The issue: teqlmasterxmit() tests the slave's ndostartxmit() return value against NETDEVTXOK alone. A slave that consumes the skb but returns an error code (rc dev and calls skbpull() on it. A VLAN slave returns the result of devqueuexmit() from its ndostartxmit() (propagated since cbbef5e18307), and when the lower qdisc drops the packet that value is NETXMITDROP after the skb has been freed, giving a use-after-free in teqlmasterxmit(). The Fix: test for consumption with devxmitcomplete(), which accepts NETDEVTXOK and every rc < NETXMITMASK, matching other callers that need to distinguish consumed results from busy. Only NETDEVTXOK keeps the packet counted in txpackets/txbytes and advances the slave; a consumed result that is neither a success nor NETXMITCN ends the attempt and is charged to txdropped, so lower-qdisc drops are no longer reported as good transmits. NETXMITCN is counted like success because it can accompany acceptance of the current packet: pfifoheaddrop drops the old head, enqueues the current skb and returns NETXMITCN. Conditions to…

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: 7 November 2026
Last updated: 7 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-99282