CVE-2006-1056

UnknownEPSS 0.45%

Last modified

CVE-2006-1056 is a vulnerability of currently unknown severity. The Linux kernel before 2.6.16.9 and the FreeBSD kernel, when running on AMD64 and other 7th and 8th generation AuthenticAMD processors, only save/restore the FOP, FIP, and FDP x87 registers in FXSAVE/FXRSTOR when an exception is pending, which allows one process to determine portions of the state of floating point instructions of other processes, which can be leveraged to obtain sensitive information such as cryptographic keys. NOTE: this is the documented behavior of AMD64 processors, but it is inconsistent with Intel processors in a security-relevant fashion that was not addressed by the kernels.. EPSS estimates a 0.45% chance of exploitation in the next 30 days.

Description

The Linux kernel before 2.6.16.9 and the FreeBSD kernel, when running on AMD64 and other 7th and 8th generation AuthenticAMD processors, only save/restore the FOP, FIP, and FDP x87 registers in FXSAVE/FXRSTOR when an exception is pending, which allows one process to determine portions of the state of floating point instructions of other processes, which can be leveraged to obtain sensitive information such as cryptographic keys. NOTE: this is the documented behavior of AMD64 processors, but it is inconsistent with Intel processors in a security-relevant fashion that was not addressed by the kernels.

Metrics

EPSS Probability
0.45%

35.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
FreebsdFreebsdAll versions
LinuxLinux Kernel<= 2.6.16.8
LinuxLinux Kernel2.6.0
LinuxLinux Kernel2.6.1
LinuxLinux Kernel2.6.2
LinuxLinux Kernel2.6.3
LinuxLinux Kernel2.6.4
LinuxLinux Kernel2.6.5
LinuxLinux Kernel2.6.6
LinuxLinux Kernel2.6.7
LinuxLinux Kernel2.6.8
LinuxLinux Kernel2.6.9
LinuxLinux Kernel2.6.10
LinuxLinux Kernel2.6.11
LinuxLinux Kernel2.6.11.1
LinuxLinux Kernel2.6.11.2
LinuxLinux Kernel2.6.11.3
LinuxLinux Kernel2.6.11.4
LinuxLinux Kernel2.6.11.5
LinuxLinux Kernel2.6.11.6
LinuxLinux Kernel2.6.11.7
LinuxLinux Kernel2.6.11.8
LinuxLinux Kernel2.6.11.9
LinuxLinux Kernel2.6.11.10
LinuxLinux Kernel2.6.11.11
LinuxLinux Kernel2.6.11.12
LinuxLinux Kernel2.6.12Rc1
LinuxLinux Kernel2.6.12.1
LinuxLinux Kernel2.6.12.2
LinuxLinux Kernel2.6.12.3
LinuxLinux Kernel2.6.12.4
LinuxLinux Kernel2.6.12.5
LinuxLinux Kernel2.6.12.6
LinuxLinux Kernel2.6.13
LinuxLinux Kernel2.6.13.1
LinuxLinux Kernel2.6.13.2
LinuxLinux Kernel2.6.13.3
LinuxLinux Kernel2.6.13.4
LinuxLinux Kernel2.6.14
LinuxLinux Kernel2.6.14.1
LinuxLinux Kernel2.6.14.2
LinuxLinux Kernel2.6.14.3
LinuxLinux Kernel2.6.14.4
LinuxLinux Kernel2.6.14.5
LinuxLinux Kernel2.6.14.6
LinuxLinux Kernel2.6.14.7
LinuxLinux Kernel2.6.15
LinuxLinux Kernel2.6.15.1
LinuxLinux Kernel2.6.15.2
LinuxLinux Kernel2.6.15.3

Showing 50 of 64 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2006-1056?
The Linux kernel before 2.6.16.9 and the FreeBSD kernel, when running on AMD64 and other 7th and 8th generation AuthenticAMD processors, only save/restore the FOP, FIP, and FDP x87 registers in FXSAVE/FXRSTOR when an exception is pending, which allows one process to determine portions of the state of floating point instructions of other processes, which can be leveraged to obtain sensitive information such as cryptographic keys. NOTE: this is the documented behavior of AMD64 processors, but it is inconsistent with Intel processors in a security-relevant fashion that was not addressed by the kernels.
How severe is CVE-2006-1056?
Severity scoring for CVE-2006-1056 is pending analysis. The EPSS model estimates a 0.45% probability of exploitation in the next 30 days.
How do I fix CVE-2006-1056?
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-2006-1056?

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

Scan your code now

Source: NVD / NIST