Skip to content
Fencer Vulns
low 2.1

CVE-2006-0095 json

dm-crypt in Linux kernel 2.6.15 and earlier does not clear a structure before it is freed, which leads to a memory disclosure that could al…

published 2006-01-06 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0103

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

dm-crypt in Linux kernel 2.6.15 and earlier does not clear a structure before it is freed, which leads to a memory disclosure that could allow local users to obtain sensitive information about a cryptographic key.

Patch / fix

  • kernel RHEL 4 2.6.9-34.EL
  • kernel-smp RHEL 4 2.6.9-34.EL
  • kernel-hugemem RHEL 4 2.6.9-34.EL
  • kernel-largesmp RHEL 4 2.6.9-34.EL

red hat advisories RHSA-2006:0132

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2006-0095 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 kernel 2.6.9-34.EL, kernel-smp 2.6.9-34.EL, kernel-hugemem 2.6.9-34.EL, kernel-largesmp 2.6.9-34.EL Red Hat Enterprise Linux Desktop version 4 kernel 2.6.9-34.EL, kernel-smp 2.6.9-34.EL, kernel-hugemem 2.6.9-34.EL, kernel-largesmp 2.6.9-34.EL Red Hat Enterprise Linux ES version 4 kernel 2.6.9-34.EL, kernel-smp 2.6.9-34.EL, kernel-hugemem 2.6.9-34.EL, kernel-largesmp 2.6.9-34.EL Red Hat Enterprise Linux WS version 4 kernel 2.6.9-34.EL, kernel-smp 2.6.9-34.EL, kernel-hugemem 2.6.9-34.EL, kernel-largesmp 2.6.9-34.EL
    fixed: vendor fix RHSA-2006:0132

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.