Kernel crash via unchecked remote-port allocation failure
Published May 21, 2024 · Updated May 11, 2026
A NULL pointer dereference in Linux allows local users to crash the kernel during Fibre Channel point-to-point remote-port setup. In fc_lport_ptp_setup(), the libfc driver fails to test whether fc_rport_create() returned NULL before dereferencing the remote-port pointer. Reaching the fault requires the libfc point-to-point path and a remote-port allocation failure; public records do not establish attacker control over that failure.
Summary
What happened
A NULL pointer dereference in Linux allows local users to crash the kernel during Fibre Channel point-to-point remote-port setup. In fc_lport_ptp_setup(), the libfc driver fails to test whether fc_rport_create() returned NULL before dereferencing the remote-port pointer. Reaching the fault requires the libfc point-to-point path and a remote-port allocation failure; public records do not establish attacker control over that failure.
The record
- CVE
- CVE-2023-52809
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.29
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <442fd24d7b6b29e4a9cd9225afba4142d5f522ba
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <4df105f0ce9f6f30cda4e99f577150d23f0c9c5f
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <56d78b5495ebecbb9395101f3be177cd0a52450b
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <6b9ecf4e1032e645873933e5b43cbb84cac19106
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <77072ec41d6ab3718c3fc639bc149b8037caedfa
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <930f0aaba4820d6362de4e6ed569eaf444f1ea4e
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <b549acf999824d4f751ca57965700372f2f3ad00
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <bb83f79f90e92f46466adcfd4fd264a7ae0f0f01
- Affected versionversion=42e9a92fe6a9095bd68a379aaec7ad2be0337f7a <f6fe7261b92b21109678747f36df9fdab1e30c34
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo