Kernel panic via unsynchronized pf state timeout updates
Published Mar 1, 2024 · Updated Nov 14, 2024
Race condition in OpenBSD 7.4 before errata 009 allows local users to crash the kernel during pf packet-state processing. Packet paths update pf_state timeout values without holding the state mutex, allowing pf_test to write a timeout after pf_purge_expired_states marks the state PFTM_UNLINKED. The affected system must process packets through pf while a state expires; the resulting assertion failure causes a system-wide crash.
Summary
What happened
Race condition in OpenBSD 7.4 before errata 009 allows local users to crash the kernel during pf packet-state processing. Packet paths update pf_state timeout values without holding the state mutex, allowing pf_test to write a timeout after pf_purge_expired_states marks the state PFTM_UNLINKED. The affected system must process packets through pf while a state expires; the resulting assertion failure causes a system-wide crash.
The record
- CVE
- CVE-2023-52556
- Published
- Mar 1, 2024
- Updated
- Nov 14, 2024
- Vendor
- OpenBSD Project
- Product
- OpenBSD
- Classifications
- CWE-367, CAPEC-29, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 2024Record 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=7.4 <7.4 errata 009
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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