CVE-2009-1360 json
The __inet6_check_established function in net/ipv6/inet6_hashtables.c in the Linux kernel before 2.6.29, when Network Namespace Support (ak…
published 2009-04-22 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1358
- cvss
- 7.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
The __inet6_check_established function in net/ipv6/inet6_hashtables.c in the Linux kernel before 2.6.29, when Network Namespace Support (aka NET_NS) is enabled, allows remote attackers to cause a denial of service (NULL pointer dereference and system crash) via vectors involving IPv6 packets.
Patch / fix
Exploit prediction
3.19% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- xorl.wordpress.com http://xorl.wordpress.com/2009/04/21/linux-kernel-net_ns-ipv6-null-pointer-dereference/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.1 | AV:N/AC:M/Au:N/C:N/I:N/A:C |
Classification
- Technology feeds
References
-
kernel.org
/pub/linux/kernel/v2.6/ChangeLog-2.6.29
patch, vendor-advisory
-
xorl.wordpress.com
/2009/04/21/linux-kernel-net_ns-ipv6-null-pointer-dereference/
exploit
-
mandriva.com
/security/advisories?name=MDVSA-2009:135
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2009-06/msg00002.html
vendor-advisory
-
ubuntu.com
/usn/usn-793-1
vendor-advisory
-
secunia.com
/advisories/35656
third-party-advisory
-
securityfocus.com
/bid/34602
vdb-entry
-
secunia.com
/advisories/35387
third-party-advisory
- git.kernel.org /?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=3f53a38131a4e7a053c0aa060aba0411242fb6b9
Sources
- CVE List CVE-2009-1360
- NVD CVE-2009-1360
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.