CVE-2011-2213

UnknownEPSS 0.41%

Last modified

CVE-2011-2213 is a vulnerability of currently unknown severity. The inet_diag_bc_audit function in net/ipv4/inet_diag.c in the Linux kernel before 2.6.39.3 does not properly audit INET_DIAG bytecode, which allows local users to cause a denial of service (kernel infinite loop) via crafted INET_DIAG_REQ_BYTECODE instructions in a netlink message, as demonstrated by an INET_DIAG_BC_JMP instruction with a zero yes value, a different vulnerability than CVE-2010-3880.. EPSS estimates a 0.41% chance of exploitation in the next 30 days.

Description

The inet_diag_bc_audit function in net/ipv4/inet_diag.c in the Linux kernel before 2.6.39.3 does not properly audit INET_DIAG bytecode, which allows local users to cause a denial of service (kernel infinite loop) via crafted INET_DIAG_REQ_BYTECODE instructions in a netlink message, as demonstrated by an INET_DIAG_BC_JMP instruction with a zero yes value, a different vulnerability than CVE-2010-3880.

Metrics

EPSS Probability
0.41%

32.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
LinuxLinux Kernel< 2.6.39.3
RedhatEnterprise Linux Aus5.6
RedhatEnterprise Linux Desktop5.0
RedhatEnterprise Linux Eus5.6
RedhatEnterprise Linux Server5.0
RedhatEnterprise Linux Workstation5.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2011-2213?
The inet_diag_bc_audit function in net/ipv4/inet_diag.c in the Linux kernel before 2.6.39.3 does not properly audit INET_DIAG bytecode, which allows local users to cause a denial of service (kernel infinite loop) via crafted INET_DIAG_REQ_BYTECODE instructions in a netlink message, as demonstrated by an INET_DIAG_BC_JMP instruction with a zero yes value, a different vulnerability than CVE-2010-3880.
How severe is CVE-2011-2213?
Severity scoring for CVE-2011-2213 is pending analysis. The EPSS model estimates a 0.41% probability of exploitation in the next 30 days.
How do I fix CVE-2011-2213?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2011-2213?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST