BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-68344High confidence

usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect

Linux · Linux

…UnscoredAssess manually
Recommended action
Needs assessment

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.22% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Manual assessmentRemediation target: Manual assessment

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

18 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-55445

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionNeeds assessment

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence.

Fix not verified
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
Not available from the selected scoring authority.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-55445Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2730Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Aug 2026, published on 12 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-68328 Référence CVE CVE-2026-68329 https://www.cve.org/CVERecord?id=CVE-2026-68329 Référence CVE CVE-2026-68331 https://www.cve.org/CVERecord?id=CVE-2026-68331 Référence CVE CVE-2026-68333 https://www.cve.org/CVERecord?id=CVE-2026-68333 Référence CVE CVE-2026-68335 https://www.cve.org/CVERecord?id=CVE-2026-68335 Référence CVE CVE-2026-68336 https://www.cve.org/CVERecord?id=CVE-2026-68336 Référence CVE CVE-2026-68338 https://www.cve.org/CVERecord?id=CVE-2026-68338 Référence CVE CVE-2026-68339 https://www.cve.org/CVERecord?id=CVE-2026-68339 Référence CVE CVE-2026-68340 https://www.cve.org/CVERecord?id=CVE-2026-68340 Référence CVE CVE-2026-68344 https://www.cve.org/CVERecord?id=CVE-2026-68344 Référence CVE CVE-2026-68346 https://www.cve.org/CVERecord?id=CVE-2026-68346 Référence CVE CVE-2026-68348 https://www.cve.org/CVERecord?id=CVE-2026-68348 Référence CVE CVE-2026-68349 https://www.cve.org/CVERecord?id=CVE-2026-68349 Référence CVE CVE-2026-68350 https://www.cve.org/CVERecord?id=CVE-2026-68350 Référence CVE CVE-2026-68351 https://www.cve.org/CVERecord?id=CVE-2026-68351 Référence CVE CVE-2026-68352 https://www.cve.org/CVERecord?id=CVE-2026-68352 Référence CVE CVE-2026-68353 https://www.cve.org/CVERecord?id=CVE-2026-68353 Référence CVE CVE-2026-68354 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1163Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-68327 Référence CVE CVE-2026-68328 https://www.cve.org/CVERecord?id=CVE-2026-68328 Référence CVE CVE-2026-68331 https://www.cve.org/CVERecord?id=CVE-2026-68331 Référence CVE CVE-2026-68333 https://www.cve.org/CVERecord?id=CVE-2026-68333 Référence CVE CVE-2026-68335 https://www.cve.org/CVERecord?id=CVE-2026-68335 Référence CVE CVE-2026-68336 https://www.cve.org/CVERecord?id=CVE-2026-68336 Référence CVE CVE-2026-68338 https://www.cve.org/CVERecord?id=CVE-2026-68338 Référence CVE CVE-2026-68340 https://www.cve.org/CVERecord?id=CVE-2026-68340 Référence CVE CVE-2026-68343 https://www.cve.org/CVERecord?id=CVE-2026-68343 Référence CVE CVE-2026-68344 https://www.cve.org/CVERecord?id=CVE-2026-68344 Référence CVE CVE-2026-68349 https://www.cve.org/CVERecord?id=CVE-2026-68349 Référence CVE CVE-2026-68350 https://www.cve.org/CVERecord?id=CVE-2026-68350 Référence CVE CVE-2026-68351 https://www.cve.org/CVERecord?id=CVE-2026-68351 Référence CVE CVE-2026-68352 https://www.cve.org/CVERecord?id=CVE-2026-68352 Référence CVE CVE-2026-68353 https://www.cve.org/CVERecord?id=CVE-2026-68353 Référence CVE CVE-2026-68354 https://www.cve.org/CVERecord?id=CVE-2026-68354 Référence CVE CVE-2026-68355 https://www.cve.org/CVERecord?id=CVE-2026-68355 Référence CVE CVE-2026-68357 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1069Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-68329 Référence CVE CVE-2026-68331 https://www.cve.org/CVERecord?id=CVE-2026-68331 Référence CVE CVE-2026-68333 https://www.cve.org/CVERecord?id=CVE-2026-68333 Référence CVE CVE-2026-68335 https://www.cve.org/CVERecord?id=CVE-2026-68335 Référence CVE CVE-2026-68336 https://www.cve.org/CVERecord?id=CVE-2026-68336 Référence CVE CVE-2026-68338 https://www.cve.org/CVERecord?id=CVE-2026-68338 Référence CVE CVE-2026-68339 https://www.cve.org/CVERecord?id=CVE-2026-68339 Référence CVE CVE-2026-68340 https://www.cve.org/CVERecord?id=CVE-2026-68340 Référence CVE CVE-2026-68343 https://www.cve.org/CVERecord?id=CVE-2026-68343 Référence CVE CVE-2026-68344 https://www.cve.org/CVERecord?id=CVE-2026-68344 Référence CVE CVE-2026-68346 https://www.cve.org/CVERecord?id=CVE-2026-68346 Référence CVE CVE-2026-68348 https://www.cve.org/CVERecord?id=CVE-2026-68348 Référence CVE CVE-2026-68349 https://www.cve.org/CVERecord?id=CVE-2026-68349 Référence CVE CVE-2026-68350 https://www.cve.org/CVERecord?id=CVE-2026-68350 Référence CVE CVE-2026-68351 https://www.cve.org/CVERecord?id=CVE-2026-68351 Référence CVE CVE-2026-68352 https://www.cve.org/CVERecord?id=CVE-2026-68352 Référence CVE CVE-2026-68353 https://www.cve.org/CVERecord?id=CVE-2026-68353 Référence CVE CVE-2026-68354 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
Linux: d85f19aaef42a03e3e4765d659c761c8750a7f23 < 9e7312844429379108ea9523a5ed934f142bb177, 76861031b43a18065d13f9ffb8595d25c7576005 < f92832262718443feb4e5df2bf70424ba842629e, bbfedc84714064ea4845e6b76f96316eb5bb65d8 < e814ae925f6f575325124c29dde518b92c822b83, f2a6abc670104fc3e383ee3b1cf35c070485e3df < c035b1198906dd5bd3df9a3045b59254bad1ea7a, c581e30ae5b332d8acef64475a211b3f82099941 < 9904a46401198872ab3de34fd11f383831ef3428, 509b51327320bdeaef1969248177a446ded073ab < d0a57f19fe2865b9747484f5f9c631f944ed9a0f, ddcdac47e1f2651c7be60e299f98faf981522797 < 0cc0c4c14150bb5a16b88dd61368f96cd4caa9ce, e2674dfbed8a30d57e2bc872c4bfa6c3eec918bf < 71132cedd1ecbc4032d76e9928c18a10f7e39b80, 5.10.261 < 5.10.265, 5.15.212 < 5.15.216, 6.1.178 < 6.1.183, 6.6.145 < 6.6.148, 6.12.97 < 6.12.101, 6.18.40 < 6.18.42, 7.1.5 < 7.1.6
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 19 Aug 2026, 16:33 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-55445
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CVSS base score, CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    f2a6abc670104fc3e383ee3b1cf35c070485e3df < c035b1198906dd5bd3df9a3045b59254bad1ea7a; c581e30ae5b332d8acef64475a211b3f82099941 < 9904a46401198872ab3de34fd11f383831ef3428; 509b51327320bdeaef1969248177a446ded073ab < d0a57f19fe2865b9747484f5f9c631f944ed9a0f; ddcdac47e1f2651c7be60e299f98faf981522797 < 0cc0c4c14150bb5a16b88dd61368f96cd4caa9ce; e2674dfbed8a30d57e2bc872c4bfa6c3eec918bf < 71132cedd1ecbc4032d76e9928c18a10f7e39b80; d85f19aaef42a03e3e4765d659c761c8750a7f23; 76861031b43a18065d13f9ffb8595d25c7576005; bbfedc84714064ea4845e6b76f96316eb5bb65d8 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    d85f19aaef42a03e3e4765d659c761c8750a7f23 < 9e7312844429379108ea9523a5ed934f142bb177; 76861031b43a18065d13f9ffb8595d25c7576005 < f92832262718443feb4e5df2bf70424ba842629e; bbfedc84714064ea4845e6b76f96316eb5bb65d8 < e814ae925f6f575325124c29dde518b92c822b83; f2a6abc670104fc3e383ee3b1cf35c070485e3df < c035b1198906dd5bd3df9a3045b59254bad1ea7a; c581e30ae5b332d8acef64475a211b3f82099941 < 9904a46401198872ab3de34fd11f383831ef3428; 509b51327320bdeaef1969248177a446ded073ab < d0a57f19fe2865b9747484f5f9c631f944ed9a0f; ddcdac47e1f2651c7be60e299f98faf981522797 < 0cc0c4c14150bb5a16b88dd61368f96cd4caa9ce; e2674dfbed8a30d57e2bc872c4bfa6c3eec918bf < 71132cedd1ecbc4032d76e9928c18a10f7e39b80 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: git.kernel.org/c035b1198906dd5bd3df9a3045b59254bad1ea7a.
    Before
    remediation: git.kernel.org/c035b1198906dd5bd3df9a3045b59254bad1ea7a
    After
    no authoritative guidance recorded
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    f2a6abc670104fc3e383ee3b1cf35c070485e3df < c035b1198906dd5bd3df9a3045b59254bad1ea7a; c581e30ae5b332d8acef64475a211b3f82099941 < 9904a46401198872ab3de34fd11f383831ef3428; 509b51327320bdeaef1969248177a446ded073ab < d0a57f19fe2865b9747484f5f9c631f944ed9a0f; ddcdac47e1f2651c7be60e299f98faf981522797 < 0cc0c4c14150bb5a16b88dd61368f96cd4caa9ce; e2674dfbed8a30d57e2bc872c4bfa6c3eec918bf < 71132cedd1ecbc4032d76e9928c18a10f7e39b80; d85f19aaef42a03e3e4765d659c761c8750a7f23; 76861031b43a18065d13f9ffb8595d25c7576005; bbfedc84714064ea4845e6b76f96316eb5bb65d8 · Fixed: < 7.2-rc3; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc5 ≤ *
    After
    f2a6abc670104fc3e383ee3b1cf35c070485e3df < c035b1198906dd5bd3df9a3045b59254bad1ea7a; c581e30ae5b332d8acef64475a211b3f82099941 < 9904a46401198872ab3de34fd11f383831ef3428; 509b51327320bdeaef1969248177a446ded073ab < d0a57f19fe2865b9747484f5f9c631f944ed9a0f; ddcdac47e1f2651c7be60e299f98faf981522797 < 0cc0c4c14150bb5a16b88dd61368f96cd4caa9ce; e2674dfbed8a30d57e2bc872c4bfa6c3eec918bf < 71132cedd1ecbc4032d76e9928c18a10f7e39b80; d85f19aaef42a03e3e4765d659c761c8750a7f23; 76861031b43a18065d13f9ffb8595d25c7576005; bbfedc84714064ea4845e6b76f96316eb5bb65d8 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  4. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-55445↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-68344 · cve.blacktree.nl