CVE-2023-34324: Possible deadlock in Linux kernel event handling
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.1% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: linux (Debian:10) 4.19.304-1; linux-5.10 (Debian:10) 5.10.205-2~deb10u1; linux (Debian:11) 5.10.205-2.
Low priority for now. Upgrade to linux (Debian:10) 4.19.304-1; linux-5.10 (Debian:10) 5.10.205-2~deb10u1; linux (Debian:11) 5.10.205-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Closing of an event channel in the Linux kernel can result in a deadlock. This happens when the close is being performed in parallel to an unrelated Xen console action and the handling of a Xen console interrupt in an unprivileged guest. The closing of an event channel is e.g. triggered by removal of a paravirtual device on the other side. As this action will cause console messages to be issued on the other side quite often, the chance of triggering the deadlock is not neglectable. Note that 32-bit Arm-guests are not affected, as the 32-bit Linux kernel on Arm doesn't use queued-RW-locks, which are required to trigger the issue (on Arm32 a waiting writer doesn't block further readers to get the lock).
- BDU:2023-06752
- DLA-3710-1
- DLA-3711-1
- DSA-5594-1
- SUSE-SU-2023:4343-1
- SUSE-SU-2023:4345-1
- SUSE-SU-2023:4346-1
- SUSE-SU-2023:4347-1
- SUSE-SU-2023:4348-1
- SUSE-SU-2023:4349-1
- SUSE-SU-2023:4351-1
- SUSE-SU-2023:4358-1
- SUSE-SU-2023:4359-1
- SUSE-SU-2023:4375-1
- SUSE-SU-2023:4377-1
- SUSE-SU-2023:4378-1
- SUSE-SU-2023:4414-1
- Published
- Jan 5, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 67th percentile
- CWE
- CWE-400
Report tools
Action score
19
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.10
- xen xenall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (XEN). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- consult Xen advisory XSA-441unknown
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | linux | before 4.19.304-1 | 4.19.304-1 |
| Debian:10 | linux-5.10 | before 5.10.205-2~deb10u1 | 5.10.205-2~deb10u1 |
| Debian:11 | linux | before 5.10.205-2 | 5.10.205-2 |
| Debian:12 | linux | before 6.1.64-1 | 6.1.64-1 |
| Debian:13 | linux | before 6.5.8-1 | 6.5.8-1 |
| openSUSE:Leap 15.4 | dtb-aarch64 | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | dtb-aarch64 | before 5.3.18-150300.59.141.1 | 5.3.18-150300.59.141.1 |
| openSUSE:Leap 15.4 | kernel-64kb | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | kernel-azure | before 5.14.21-150400.14.72.1 | 5.14.21-150400.14.72.1 |
| openSUSE:Leap 15.4 | kernel-debug | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | kernel-debug | before 4.12.14-150100.197.160.1 | 4.12.14-150100.197.160.1 |
| openSUSE:Leap 15.4 | kernel-default | before 4.12.14-150100.197.160.1 | 4.12.14-150100.197.160.1 |
| openSUSE:Leap 15.4 | kernel-docs | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | kernel-kvmsmall | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | kernel-kvmsmall | before 4.12.14-150100.197.160.1 | 4.12.14-150100.197.160.1 |
| openSUSE:Leap 15.4 | kernel-obs-build | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | kernel-obs-qa | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | kernel-rt_debug | before 5.14.21-150400.15.59.1 | 5.14.21-150400.15.59.1 |
| openSUSE:Leap 15.4 | kernel-source | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | kernel-source-azure | before 5.14.21-150400.14.72.1 | 5.14.21-150400.14.72.1 |
| openSUSE:Leap 15.4 | kernel-source-rt | before 5.14.21-150400.15.59.1 | 5.14.21-150400.15.59.1 |
| openSUSE:Leap 15.4 | kernel-syms | before 5.14.21-150400.24.97.1 | 5.14.21-150400.24.97.1 |
| openSUSE:Leap 15.4 | kernel-syms-azure | before 5.14.21-150400.14.72.1 | 5.14.21-150400.14.72.1 |
| openSUSE:Leap 15.4 | kernel-syms-rt | before 5.14.21-150400.15.59.1 | 5.14.21-150400.15.59.1 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-7192Jan 2, 2024 · Kernel: refcount leak in ctnetlink_create_conntrack()17Monitor
- ← EarlierCVE-2023-6270Jan 4, 2024 · Kernel: aoe: improper reference count leads to use-after-free vulnerability28Monitor
- Later →CVE-2022-2585Jan 8, 2024 · It was discovered that when exec'ing from a non-leader thread, armed POSIX CPU timers would be left on a list but freed, leading to a use-af31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:linux | 6.1.64-1 · Debian:12 | Package registry (OSV) |
| debian:linux-5.10 | 5.10.205-2~deb10u1 · Debian:10 | Package registry (OSV) |
| opensuse:kernel-azure | 5.14.21-150400.14.72.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-debug | 4.12.14-150100.197.160.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-default | 4.12.14-150100.197.160.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 4.12.14-150100.197.160.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150500.13.24.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 5.14.21-150500.13.24.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-azure | 5.14.21-150400.14.72.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-source-rt | 5.14.21-150500.13.24.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 5.14.21-150400.14.72.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 5.14.21-150500.13.24.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-vanilla | 4.12.14-150100.197.160.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:kernel-zfcpdump | 4.12.14-150100.197.160.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| suse:kernel-azure | 5.14.21-150400.14.72.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-150100.197.160.1 · SUSE:Linux Enterprise Live Patching 15 SP1 | Package registry (OSV) |
| suse:kernel-docs | 4.12.14-150100.197.160.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP1_Update_45 | 1-150100.3.3.1 · SUSE:Linux Enterprise Live Patching 15 SP1 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5-RT_Update_7 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 4.12.14-150100.197.160.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150500.13.24.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-rt_debug | 5.14.21-150500.13.24.1 · SUSE:Real Time Module 15 SP5 | Package registry (OSV) |
| suse:kernel-source-azure | 5.14.21-150400.14.72.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150500.13.24.1 · SUSE:Real Time Module 15 SP5 | Package registry (OSV) |
| suse:kernel-syms-azure | 5.14.21-150400.14.72.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:kernel-syms-rt | 5.14.21-150500.13.24.1 · SUSE:Real Time Module 15 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- This issue was discovered as a bug by Marek Marczykowski-GóreckiInvisible Things Lab; the security impact was recognised by Jürgen Groß of SUSE.finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-39462172 days apartclk: bcm: dvp: Assign ->num before accessing ->hws39Monitor
- CVE-2021-4440172 days apartx86/xen: Drop USERGS_SYSRET64 paravirt call35Monitor
- CVE-2021-47313137 days apartcpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init33Monitor
- CVE-2021-4702354 days apartnet: marvell: prestera: fix port event handling on init32Monitor
- CVE-2024-38616166 days apartwifi: carl9170: re-fix fortified-memset warning32Monitor
- CVE-2021-4701054 days apartnet: Only allow init netns to set default tcp cong to a restricted algo31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.