Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-1095 is a medium-severity NULL Pointer Dereference (CWE-476) vulnerability in Linux Kernel. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-23382
Vulnerability Data
In nf_tables_updtable, if nf_tables_table_enable returns an error, nft_trans_destroy is called to free the transaction object. nft_trans_destroy() calls list_del(), but the transaction was never placed on a list -- the list head is all zeroes, this results in a NULL pointer…
more
dereference.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices (static analysis, code review, safe coding standards) directly prevent NULL dereference bugs during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect NULL dereference defects before release.
Secure coding standards directly require NULL-pointer checks and safe dereference patterns.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation defects like NULL pointer dereferences in delivered code the way those practices do, at `partial` — the clause depends on the supplier actually implementing secure coding and testing, and fallible developers still introduce these defects.
A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. NULL pointer dereferences do commonly surface as CVEs (many examples in CWE-476's observed examples), so the disclosed share is non-trivial, but it remains a minority of all instances: most CWE-476 flaws live in first-party code that nobody has published an advisory about, and A.8.8's scanning and patching programme does not read source.