Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the SL811 USB driver cleanup path. A local authenticated user could contribute to resource exhaustion over time, potentially causing availability impact. The issue is rated medium and the source bundle does not show active exploitation.
Executive priority
Treat as a routine but real availability risk. Patch during the next kernel maintenance window, sooner on shared systems with untrusted local users or sensitive uptime requirements.
Technical view
The SL811 USB code used debugfs_lookup() without releasing the returned reference with dput(). The kernel fix replaces that flow with debugfs_lookup_and_remove(), avoiding a leaked reference during debugfs cleanup. CVSS 3.1 is 5.5 with local, low-privilege availability impact only.
Likely exposure
Likely exposure is Linux systems running affected kernel versions that include the vulnerable SL811 USB driver code. Confirm through distribution kernel advisories because vendor kernels may backport fixes without changing upstream version numbers.
Exploitation context
The source bundle marks KEV as false and provides no public evidence of exploitation. The CVSS vector requires local access with low privileges and indicates no confidentiality or integrity impact, but high availability impact.
Researcher notes
Evidence supports a reference leak in debugfs cleanup for the Linux SL811 USB driver. The bundle does not identify exploit PoC, active abuse, or downstream distribution fix versions, so validation should rely on vendor backport status.
Mitigation direction
- Update to a vendor kernel package that includes the upstream stable fix.
- Check distribution guidance for backported fixed kernel versions.
- Review whether SL811 USB support is present and needed on affected systems.
- Prioritize remediation on systems where local users or workloads are untrusted.
Validation and detection
- Map running kernels to affected and fixed vendor package versions.
- Confirm whether SL811 USB driver code is built, loaded, or in use.
- Verify the fixed code path uses debugfs_lookup_and_remove().
- Run standard kernel regression testing for USB and debugfs behavior after update.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-401: 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.
Open ATT&CK lookupCVE-2023-53417 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/bb4d5eefb67095d7c3b70b08498b23b7f2895f76CVE reference, Linux
- https://git.kernel.org/stable/c/54166af8941d0cf46b65cfa2fbce76e38d82fadfCVE reference, Linux
- https://git.kernel.org/stable/c/04fdfec7b0286972cb5457ef958c92585447a39fCVE reference, Linux
- https://git.kernel.org/stable/c/e1523c4dbc54e164638ff8729d511cf91e27be04CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.