Security readout for executives and security teams
Plain-English summary
This is a Linux kernel loop-device issue that can affect system availability. The record describes a lifetime and locking problem where loop-device private data could become unsafe before the disk object is fully freed. It is local, requires some privilege, and does not indicate data theft or data modification.
Executive priority
Treat as a moderate operational stability risk. It is not described as remotely exploitable and has no cited active exploitation, but Linux kernel availability issues can matter on shared servers, CI hosts, and systems with local user access.
Technical view
The loop driver needed a free_disk handler so lo_device stored in gendisk private data remains valid until gendisk release. The CVE is classified as CWE-667 with CVSS 5.5: local attack vector, low complexity, low privileges, no user interaction, and high availability impact only.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions and using loop block devices. The source bundle does not identify affected distributions, cloud images, appliances, or container-specific conditions, so asset owners should map kernel versions against vendor advisories.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. The CVSS vector indicates local, low-privilege exploitation potential with availability impact. No public exploit status is provided in the supplied evidence.
Researcher notes
Evidence is limited to the CVE record and Linux stable commits. The root issue is object lifetime around gendisk private data in the loop driver, tied to locking behavior. Do not infer distro impact, exploit availability, or mitigations beyond kernel updates and vendor guidance.
Mitigation direction
- Apply kernel updates containing the referenced stable fixes.
- Check distribution vendor advisories for backported kernel packages.
- Prioritize hosts where untrusted local users can access loop-device workflows.
- Avoid assuming package version numbers match upstream kernel versions.
- Monitor vendor guidance for any additional hardening recommendations.
Validation and detection
- Inventory Linux kernel versions across affected assets.
- Identify systems using or exposing loop block devices.
- Confirm installed kernels include vendor fixes for CVE-2022-49531.
- Review vendor security advisories for backport confirmation.
- Validate that rebooted systems are running the updated kernel.
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-667: 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-49531 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/aadd1443aae7fe8956e3b11157827067f034406aCVE reference, Linux
- https://git.kernel.org/stable/c/d2c7f56f8b5256d57f9e3fc7794c31361d43bdd9CVE 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.
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.