In the Linux kernel, the following vulnerability has been resolved:
scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write
During the sysfs firmware write process, a use-after-free read warning is
logged from the lpfc_wr_object() routine:
BUG: KFENCE: use-after-free read in lpfc_wr_object+0x235/0x310 [lpfc]
Use-after-free read at 0x0000000000cf164d (in kfence-#111):
lpfc_wr_object+0x235/0x310 [lpfc]
lpfc_write_firmware.cold+0x206/0x30d [lpfc]
lpfc_sli4_request_firmware_update+0xa6/0x100 [lpfc]
lpfc_request_firmware_upgrade_store+0x66/0xb0 [lpfc]
kernfs_fop_write_iter+0x121/0x1b0
new_sync_write+0x11c/0x1b0
vfs_write+0x1ef/0x280
ksys_write+0x5f/0xe0
do_syscall_64+0x59/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
The driver accessed wr_object pointer data, which was initialized into
mailbox payload memory, after the mailbox object was released back to the
mailbox pool.
Fix by moving the mailbox free calls to the end of the routine ensuring
that we don't reference internal mailbox memory after release.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53282 is a Linux kernel use-after-free bug in the lpfc SCSI driver during a sysfs-triggered firmware write. A local, low-privileged attacker could potentially impact confidentiality, integrity, and availability. The issue is not listed as known exploited in CISA KEV in the provided data.
Executive priority
Treat as high priority for Linux servers that use lpfc-based storage connectivity, especially multi-user systems. This is local, not remotely exploitable based on provided evidence, so prioritize after internet-facing critical issues but before routine maintenance where the driver is present.
Technical view
The lpfc_wr_object() routine could read mailbox payload data after the mailbox object was returned to the pool. The kernel fix moves mailbox free calls to the end of the routine, preventing references to internal mailbox memory after release. The CVSS v3.1 score is 7.8 with local attack vector and low privileges required.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the lpfc driver and access to the sysfs firmware update path. Systems not using this driver or not permitting local users to reach the relevant firmware-write interface are less likely exposed.
Exploitation context
The provided sources describe a local vulnerability requiring low privileges and no user interaction. They do not provide evidence of active exploitation, public exploit availability, or remote attackability. The practical risk depends on local account access, driver presence, and kernel version.
Researcher notes
The CVE record maps this to CWE-416 and CVSS 7.8. Version data in the provided bundle is not sufficient to create a complete affected-version matrix. Validate against distribution advisories and the referenced stable commits before declaring systems fixed or vulnerable.
Mitigation direction
Update to a kernel or vendor package containing the referenced upstream stable fixes.
Prioritize servers using the lpfc driver or Fibre Channel storage paths.
Restrict local user access to sensitive administrative interfaces where possible.
Check Linux distribution advisories for backported fixes and supported update packages.
Validation and detection
Inventory Linux kernel versions across affected server fleets.
Identify systems where the lpfc driver is present or loaded.
Confirm whether vendor kernels include the referenced stable commits or backports.
Review kernel logs for related KFENCE or use-after-free warnings.
Track remediation through package versions, not only upstream kernel numbers.
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.
cwe · low confidence lookup
CWE-416: 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.
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.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.