CVE-2022-50148: kernfs: fix potential NULL dereference in __kernfs_remove
In the Linux kernel, the following vulnerability has been resolved:
kernfs: fix potential NULL dereference in __kernfs_remove
When lockdep is enabled, lockdep_assert_held_write would
cause potential NULL pointer dereference.
Fix the following smatch warnings:
fs/kernfs/dir.c:1353 __kernfs_remove() warn: variable dereferenced before check 'kn' (see line 1346)
Security readout for executives and security teams
Plain-English summary
CVE-2022-50148 is a Linux kernel kernfs bug that can cause a NULL pointer dereference in removal logic when lockdep is enabled. The public record does not provide CVSS, CWE, or impact details, so business urgency should be driven by affected kernel inventory and vendor kernel guidance.
Executive priority
Set priority after confirming affected kernels. With no CVSS, KEV listing, or exploit evidence, this is not clearly business-critical, but kernel bugs deserve timely remediation through normal patch governance, especially on shared infrastructure and security-sensitive hosts.
Technical view
The flaw is in fs/kernfs/dir.c within __kernfs_remove. The record states lockdep_assert_held_write may dereference kn before checking it for NULL, matching smatch warnings. Linux lists affected kernel ranges and stable commit references, but the bundle does not describe privilege requirements, triggerability, or security impact beyond NULL dereference.
Likely exposure
Exposure is most likely on systems running affected Linux kernel versions or downstream kernels that include the vulnerable kernfs code. The record specifically mentions lockdep-enabled behavior, so standard production kernels may differ by vendor configuration. Confirm through distribution advisories and kernel package changelogs.
Exploitation context
The source bundle does not report active exploitation, public exploit availability, or inclusion in CISA KEV. It also does not provide exploit preconditions. Treat this as an inventory and patch-validation item, not an emergency exploitation event based on current evidence.
Researcher notes
Evidence is limited to the CVE description and upstream stable commit references. The record identifies a NULL dereference condition in __kernfs_remove involving lockdep_assert_held_write, but does not establish exploitability, impact scope, or affected downstream distributions. Avoid overstating risk without vendor advisories or crash reproduction data.
Mitigation direction
Check Linux distribution advisories for CVE-2022-50148 fixed kernel packages.
Prioritize kernel updates that include the listed stable kernfs fixes.
Where feasible, avoid enabling lockdep on affected kernels pending vendor guidance.
Track vendor backports rather than relying only on upstream version numbers.
Validation and detection
Identify Linux kernel versions running across servers, appliances, and container hosts.
Check vendor package changelogs for CVE-2022-50148 or the referenced stable commits.
Confirm whether affected systems use kernels built with lockdep enabled.
Verify patched systems rebooted into the updated kernel version.
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.
cve · low confidence lookup
CVE-2022-50148 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
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.
Jun 18, 2025, 11:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.