LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54192: f2fs: fix null pointer panic in tracepoint in __replace_atomic_write_block

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix null pointer panic in tracepoint in __replace_atomic_write_block We got a kernel panic if old_addr is NULL. https://bugzilla.kernel.org/show_bug.cgi?id=217266 BUG: kernel NULL pointer dereference, address: 0000000000000000 Call Trace: <TASK> f2fs_commit_atomic_write+0x619/0x990 [f2fs a1b985b80f5babd6f3ea778384908880812bfa43] __f2fs_ioctl+0xd8e/0x4080 [f2fs a1b985b80f5babd6f3ea778384908880812bfa43] ? vfs_write+0x2ae/0x3f0 ? vfs_write+0x2ae/0x3f0 __x64_sys_ioctl+0x91/0xd0 do_syscall_64+0x5c/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc RIP: 0033:0x7f69095fe53f

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel F2FS bug that can crash the kernel when a null address reaches an F2FS tracepoint during atomic write handling. The available sources describe a kernel panic, not data theft or remote code execution. Business impact is mainly service interruption on affected Linux systems using F2FS.

Executive priority

Treat this as a patch-planning item for Linux hosts using F2FS, especially availability-sensitive systems. It is not currently supported as an internet-scale emergency by the supplied sources, but kernel panics can still cause outages and should enter normal vulnerability remediation queues.

Technical view

CVE-2023-54192 is a null pointer dereference in F2FS, fixed in __replace_atomic_write_block tracepoint handling. The reported call trace reaches f2fs_commit_atomic_write through an ioctl path, causing a kernel NULL pointer panic when old_addr is NULL. Public metadata lists Linux kernel version ranges and stable commits.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with F2FS in use. The ioctl call trace suggests local interaction with an F2FS filesystem, but the source bundle does not fully define required privileges, configuration, or distribution-specific package status.

Exploitation context

CISA KEV is false, and the source bundle provides no evidence of active exploitation or public weaponization. The described failure mode is kernel panic, so assess it primarily as a local denial-of-service stability risk unless later vendor advisories expand the impact.

Researcher notes

The strongest evidence is the kernel description and stable commit references. CVSS, CWE, privilege requirements, and distribution package mappings are absent. The local ioctl context is inferred from the call trace, so validation should focus on kernel version, F2FS usage, and vendor-published fixed builds.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable F2FS fixes.
  • Check distribution security advisories for the exact fixed kernel package.
  • Prioritize hosts that mount or rely on F2FS filesystems.
  • Review vendor guidance before applying operational workarounds.
  • Avoid direct wrangler or deployment actions; this CVE is kernel-level, not application-level.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Identify systems using mounted F2FS filesystems.
  • Compare kernels against affected versions and referenced stable commits.
  • Confirm patched packages through vendor or distribution advisories.
  • Review logs for F2FS NULL pointer panic signatures.
Prepared
Confidence
medium
Sources
6

Public sources used

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-2023-54192 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9ad51915f4b368eef8f4cbd3a0b6367d4504c245, f955d66b179679312310d42108c0df1cd0714313, 2f3a9ae990a7881c9a57a073bb52ebe34fdc3160, 2f3a9ae990a7881c9a57a073bb52ebe34fdc3160, 6.1.18, 6.2.5unaffected
LinuxLinux6.3, 0, 6.1.29, 6.2.16, 6.3.3, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.