CVE-2023-2269 — A denial of service problem was found, due to a possible recursive locking scenario…
A denial of service problem was found, due to a possible recursive locking scenario, resulting in a deadlock in table_clear in drivers/md/dm-ioctl.c in the Linux Kernel Device Mapper-Multipathing sub-component.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Fedoraproject Fedora, Linux Linux Kernel…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 10.0version 11.0version 12.0 | Vulnerable | NIST National Vulnerability Database |
| Fedoraproject | Fedora | version 36version 37version 38 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux Kernel | version 6.2 | Vulnerable | NIST National Vulnerability Database |
| Netapp | H300s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410c Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H500s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H700s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.4 | CVSS 3.1 | Medium | 0.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- CVSS changed · 4.4
- Source status changed · → Modified
- Record created in this database
- 2023
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- lore.kernel.org/lkml/ZD1xyZxb3rHot8PV%40redhat.com/t/
- lists.debian.org/debian-lts-announce/2023/10/msg00027.html
- security.netapp.com/advisory/ntap-20230929-0004/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FBLB
- www.debian.org/security/2023/dsa-5480
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/63AJ
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IXHB
- www.debian.org/security/2023/dsa-5448
- lists.debian.org/debian-lts-announce/2023/07/msg00030.html
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-98164 KVM: x86/mmu: Check write tracking in all address spaces 16d
- High CVE-2026-98163 cgroup: Avoid iteration of dying tasks with zero refcount 19d
- Medium CVE-2026-98162 smb/server: fix tree connection leak in smb2_tree_connect() 20d
- High CVE-2026-98156 drm/virtio: use the DMA API for resource backing on Xen 20d
- Medium CVE-2026-98159 wifi: mt76: mt7921: validate CLC firmware records 20d
- Medium CVE-2026-98137 ntfs: treat any nonzero dio zero-range return as an error 20d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-2269 is "A denial of service problem was found, due to a possible recursive locking scenario…", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.4 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.