7.9 High
AI Score
Confidence
High
10 High
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:N/C:C/I:C/A:C
0.949 High
EPSS
Percentile
99.3%
NFS did not correctly handle races between fcntl and interrupts. A local
attacker on an NFS mount could consume unlimited kernel memory, leading to
a denial of service. (CVE-2008-4307)
Sparc syscalls did not correctly check mmap regions. A local attacker could
cause a system panic, leading to a denial of service. (CVE-2008-6107)
In certain situations, cloned processes were able to send signals to parent
processes, crossing privilege boundaries. A local attacker could send
arbitrary signals to parent processes, leading to a denial of service.
(CVE-2009-0028)
The 64-bit syscall interfaces did not correctly handle sign extension. A
local attacker could make malicious syscalls, possibly gaining root
privileges. The x86_64 architecture was not affected. (CVE-2009-0029)
The SCTP stack did not correctly validate FORWARD-TSN packets. A remote
attacker could send specially crafted SCTP traffic causing a system crash,
leading to a denial of service. (CVE-2009-0065)
The Dell platform device did not correctly validate user parameters. A
local attacker could perform specially crafted reads to crash the system,
leading to a denial of service. (CVE-2009-0322)
Network interfaces statistics for the SysKonnect FDDI driver did not check
capabilities. A local user could reset statistics, potentially interfering
with packet accounting systems. (CVE-2009-0675)
The getsockopt function did not correctly clear certain parameters. A local
attacker could read leaked kernel memory, leading to a loss of privacy.
(CVE-2009-0676)
The syscall interface did not correctly validate parameters when crossing
the 64-bit/32-bit boundary. A local attacker could bypass certain syscall
restricts via crafted syscalls. (CVE-2009-0834, CVE-2009-0835)
The shared memory subsystem did not correctly handle certain shmctl calls
when CONFIG_SHMEM was disabled. Ubuntu kernels were not vulnerable, since
CONFIG_SHMEM is enabled by default. (CVE-2009-0859)
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
Ubuntu | 6.06 | noarch | linux-image-2.6.15-54-hppa64 | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | acpi-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | cdrom-core-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | crc-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | ext2-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | ext3-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | fat-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | fb-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | firewire-core-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
Ubuntu | 6.06 | noarch | floppy-modules-2.6.15-54-amd64-generic-di | < 2.6.15-54.76 | UNKNOWN |
ubuntu.com/security/CVE-2008-4307
ubuntu.com/security/CVE-2008-6107
ubuntu.com/security/CVE-2009-0028
ubuntu.com/security/CVE-2009-0029
ubuntu.com/security/CVE-2009-0065
ubuntu.com/security/CVE-2009-0322
ubuntu.com/security/CVE-2009-0675
ubuntu.com/security/CVE-2009-0676
ubuntu.com/security/CVE-2009-0834
ubuntu.com/security/CVE-2009-0835
ubuntu.com/security/CVE-2009-0859