Skip to main content
VulnerabilityPublished Updated

CVE-2026-68344: Linux kernel · usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f92832262718443feb4e5df2bf70424ba842629e : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f92832262718443feb4e5df2bf70424ba842629e, e814ae925f6f575325124c29dde518b92c822b83, d0a57f19fe2865b9747484f5f9c631f944ed9a0f +12

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 76861031b43a18065d13f9ffb8595d25c7576005, < f92832262718443feb4e5df2bf70424ba842629e
Fixed in
  • f92832262718443feb4e5df2bf70424ba842629e
LinuxLinuxAffected
  • ≥ bbfedc84714064ea4845e6b76f96316eb5bb65d8, < e814ae925f6f575325124c29dde518b92c822b83
Fixed in
  • e814ae925f6f575325124c29dde518b92c822b83
LinuxLinuxAffected
  • ≥ 509b51327320bdeaef1969248177a446ded073ab, < d0a57f19fe2865b9747484f5f9c631f944ed9a0f
Fixed in
  • d0a57f19fe2865b9747484f5f9c631f944ed9a0f
LinuxLinuxAffected
  • ≥ f2a6abc670104fc3e383ee3b1cf35c070485e3df, < c035b1198906dd5bd3df9a3045b59254bad1ea7a
Fixed in
  • c035b1198906dd5bd3df9a3045b59254bad1ea7a
LinuxLinuxAffected
  • ≥ e2674dfbed8a30d57e2bc872c4bfa6c3eec918bf, < 71132cedd1ecbc4032d76e9928c18a10f7e39b80
Fixed in
  • 71132cedd1ecbc4032d76e9928c18a10f7e39b80
LinuxLinuxAffected
  • ≥ c581e30ae5b332d8acef64475a211b3f82099941, < 9904a46401198872ab3de34fd11f383831ef3428
Fixed in
  • 9904a46401198872ab3de34fd11f383831ef3428

Description

In the Linux kernel, the following vulnerability has been resolved: usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect uea_probe() distinguishes a pre-firmware device from a post-firmware one using the USB id (UEA_IS_PREFIRM()), and stores a different object as the interface data in each case: a 'struct completion' for a pre-firmware device (to be waited on in .disconnect()), or a 'struct usbatm_data' for a post-firmware one. uea_disconnect() instead tells the two apart by the number of interfaces of the active configuration (a pre-firmware device exposes a single interface, ADI930 has 2 and eagle has 3), and casts the interface data accordingly. Because the two handlers use different criteria, a crafted device that advertises a pre-firmware id together with a multi-interface descriptor (or a post-firmware id with a single interface) makes them disagree: the small 'struct completion' stored by uea_probe() is then passed to usbatm_usb_disconnect(), which casts it to 'struct usbatm_data' and takes instance->serialize, reading past the end of the allocation: BUG: KASAN: slab-out-of-bounds in __mutex_lock+0x152a/0x1b80 Read of size 8 at addr ffff8880470e2c60 by task kworker/1:2/982 ... __mutex_lock+0x152a/0x1b80 usbatm_usb_disconnect+0x70/0x820 uea_disconnect+0x133/0x2c0 usb_unbind_interface+0x1dd/0x9e0 ... which belongs to the cache kmalloc-96 of size 96 The buggy address is located 0 bytes to the right of allocated 96-byte region [ffff8880470e2c00, ffff8880470e2c60) Reject such inconsistent descriptors in uea_probe() so that both handlers always make the same pre/post-firmware decision.

References

Community reviews

Loading reviews…