Security readout for executives and security teams
Plain-English summary
This is a Linux kernel resource-leak bug. If a local low-privileged user can trigger the failing disk-add path, kernel memory allocated for writeback throttling may not be released. The business risk is availability: repeated failures could contribute to memory exhaustion or instability.
Executive priority
Treat as moderate priority. It is availability-focused and local, with no cited active exploitation, but kernel memory leaks can matter on shared or high-availability systems. Patch through normal kernel maintenance, faster where untrusted local access exists.
Technical view
device_add_disk() could leak rq_wb memory allocated by wbt_enable_default() when add_disk failed. The normal del_gendisk() path calls rq_qos_exit(), but the error path only called blk_unregister_queue(). The fix adds rq_qos_exit() on that error path. CVSS is 5.5 with local, low-complexity, low-privilege availability impact.
Likely exposure
Exposure is limited to affected Linux kernel builds identified by the CVE data, including 5.15-era and 6.0/6.1 entries. Distribution backports may change practical exposure, so kernel package status must be checked against vendor advisories and the referenced stable commits.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. The CVSS vector requires local access and low privileges, with no user interaction. The public description shows a kernel memory leak in an error path, not remote code execution or data theft.
Researcher notes
The key behavior is missing cleanup on the device_add_disk() failure path after rq_wb allocation. Evidence supports CWE-401 and availability impact. The bundle does not provide proof of exploitation, distro package status, or non-Linux affected products.
Mitigation direction
- Update to a vendor-supported kernel containing the referenced stable fixes.
- Check distribution advisories for backported fixes before relying on version numbers alone.
- Prioritize multi-user systems where local users can exercise block-device paths.
- If no vendor fix is available, monitor vendor guidance for supported mitigations.
Validation and detection
- Inventory running Linux kernel versions across servers, containers hosts, and appliances.
- Map each kernel package to vendor advisories and the referenced stable commits.
- Confirm whether the rq_qos_exit() error-path fix is present in source or changelog.
- Review system exposure to local untrusted users or delegated device-management capabilities.
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-2022-49902 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/4e68c5da60cd79950bd56287ae80b39d6261f995CVE reference, Linux
- https://git.kernel.org/stable/c/528677d3b4af985445bd4ac667485ded1ed11220CVE reference, Linux
- https://git.kernel.org/stable/c/fa81cbafbf5764ad5053512152345fab37a1fe18CVE 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.