Security readout for executives and security teams
Plain-English summary
This is a Linux kernel F2FS filesystem flaw where lock initialization happened too late during filesystem setup error handling. A local low-privileged user could potentially trigger a system availability impact. The CVE is not listed as KEV, and the provided sources do not show active exploitation.
Executive priority
Treat this as a moderate Linux platform maintenance issue. It is mainly an availability risk requiring local access, not a confirmed remote breach path. Prioritize shared Linux hosts and systems using F2FS, then remediate through normal kernel patch cycles.
Technical view
The issue is in f2fs_fill_super(): f2fs_handle_error() could take sbi->error_lock before spin_lock_init() initialized it. The kernel fix moves lock and related structure initialization immediately after allocation. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is most relevant to Linux systems running affected kernels with F2FS support or F2FS filesystems in use. Distro kernels may have backported fixes, so version strings alone are insufficient. Internet-facing exposure is not indicated because the CVSS vector is local.
Exploitation context
The supplied sources describe a syzbot-reported lockdep warning and a kernel fix. They do not provide evidence of public exploitation, KEV listing, remote attack paths, or weaponized proof-of-concept activity.
Researcher notes
Evidence is limited to the CVE record and kernel stable commits. The root cause is lock ordering/initialization timing in F2FS error handling. Avoid assuming exploitability beyond the CVSS local availability impact without additional kernel or distro analysis.
Mitigation direction
- Update to a kernel containing the referenced stable fixes or equivalent distro backport.
- Check Linux distribution security advisories for patched kernel package names.
- Reduce untrusted local shell access on systems using F2FS until patched.
- Avoid enabling or relying on F2FS where business need is unclear.
- Follow vendor guidance if no patched package is currently available.
Validation and detection
- Inventory Linux kernels and identify hosts with F2FS enabled or in use.
- Confirm deployed kernels include the referenced stable commits or equivalent backports.
- Check vulnerability scanner findings against distro-specific kernel package versions.
- Prioritize validation on shared systems with untrusted local users.
- Document any systems awaiting vendor kernel updates and compensating controls.
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-49742 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/ddeff03bb33810fcf2f0c18e03d099cf0aacda62CVE reference, Linux
- https://git.kernel.org/stable/c/92b4cf5b48955a4bdd15fe4e2067db8ebd87f04cCVE 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.