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

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

CVE-2026-99271 affects Linux Linux.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: ALSA: line6: Clear prevfbuf on capture buffer release A KASAN…

CVE-2026-99271

In the Linux kernel, the following vulnerability has been resolved: ALSA: line6: Clear prevfbuf on capture buffer release A KASAN slab-use-after-free read was reported in submitaudioouturb() when generating an impulse test signal: BUG: KASAN: slab-use-after-free in createimpulsetestsignal sound/usb/line6/playback.c:76 [inline] BUG: KASAN: slab-use-after-free in submitaudioouturb+0x1848/0x1b20 sound/usb/line6/playback.c:249 Read of size 2 at addr ffff888008d74870 by task syz.2.3214/7785 Allocated by task 11: kmemcacheallocnoprof+0x2f0/0x390 mm/slub.c:4144 line6bufferacquire+0x1a1/0x220 sound/usb/line6/pcm.c:158 line6pcmacquire+0xb6/0x230 sound/usb/line6/pcm.c:329 line6startupwork+0x3c/0x50 sound/usb/line6/driver.c:728 Freed by task 7785: kfree+0xf8/0x390 mm/slub.c:6566 line6bufferrelease sound/usb/line6/pcm.c:176 [inline] line6bufferrelease+0xa5/0xf0 sound/usb/line6/pcm.c:170 line6pcmrelease sound/usb/line6/pcm.c:305 [inline] line6pcmrelease+0x5a/0x80 sound/usb/line6/pcm.c:313 sndtoneportmonitorput+0x11b/0x190 sound/usb/line6/toneport.c:183 line6pcm->prevfbuf points into the capture PCM stream buffer (line6pcm->in.buffer), which is updated during audioincallback() to feed rate…

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 3 + 4? *

Query this programmatically

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

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