In the Linux kernel, the following vulnerability has been resolved:
net: usb: lan78xx: Fix double free issue with interrupt buffer allocation
In lan78xx_probe(), the buffer `buf` was being freed twice: once
implicitly through `usb_free_urb(dev->urb_intr)` with the
`URB_FREE_BUFFER` flag and again explicitly by `kfree(buf)`. This caused
a double free issue.
To resolve this, reordered `kmalloc()` and `usb_alloc_urb()` calls to
simplify the initialization sequence and removed the redundant
`kfree(buf)`. Now, `buf` is allocated after `usb_alloc_urb()`, ensuring
it is correctly managed by `usb_fill_int_urb()` and freed by
`usb_free_urb()` as intended.
Security readout for executives and security teams
Plain-English summary
CVE-2024-53213 is a Linux kernel flaw in the lan78xx USB Ethernet driver. A memory buffer can be freed twice during device setup, creating a high-severity local risk. The provided sources do not show active exploitation, but affected Linux systems should receive vendor kernel updates.
Executive priority
Treat as a high-priority kernel maintenance item, especially on shared Linux systems. There is no sourced evidence of active exploitation, so urgency is driven by local privilege risk and kernel memory safety impact rather than an ongoing campaign.
Technical view
The issue is CWE-415 double free in lan78xx_probe(). The interrupt buffer was released through usb_free_urb() with URB_FREE_BUFFER and again by kfree(). Kernel stable commits remove the redundant free by changing allocation order and ownership handling.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds with the lan78xx USB network driver present or usable. The CVSS vector is local, low complexity, low privilege, no user interaction, with high confidentiality, integrity, and availability impact.
Exploitation context
The bundle does not cite public exploitation or CISA KEV listing. Risk is local, not network-originated according to the CVSS vector. Practical exploitability depends on affected kernel version, driver reachability, and local privilege context.
Researcher notes
Do not assume remote exposure. Focus validation on kernel version, lan78xx driver availability, and distribution backports. The source bundle gives multiple stable commit references but incomplete product-package mapping, so rely on vendor advisories for exact remediation state.
Mitigation direction
Apply vendor-supported Linux kernel updates containing the lan78xx fix.
For Debian LTS systems, review and apply the referenced Debian security update.
Prioritize systems where untrusted users can access affected hosts.
Restrict unnecessary local access until kernel remediation is complete.
Check distribution advisories for exact fixed package versions.
Validation and detection
Inventory Linux kernel versions across affected assets.
Check whether lan78xx driver support is present or loaded.
Map systems against vendor advisories and kernel stable fixes.
Confirm patched kernels are installed and active after reboot.
Document exceptions where vendor guidance is not yet available.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.