Linux KernelOperating system · Linux
CVE-2007-4567
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe ipv6_hop_jumbo function in net/ipv6/exthdrs.c in the Linux kernel before 2.6.22 does not properly validate the hop-by-hop IPv6 extended header, which allows remote attackers to cause a denial of service (NULL pointer dereference and kernel panic) via a crafted IPv6 packet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ipv6_hop_jumbo function in net/ipv6/exthdrs.c in Linux kernel before 2.6.22 fails to properly validate the hop-by-hop IPv6 extended header. This allows remote attackers to trigger a NULL pointer dereference by sending specially crafted IPv6 packets with malformed jumbo payload options, resulting in kernel panic and denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
<= 2.6.21.7= 2.2.27= 2.4.36= 2.4.36.1= 2.4.36.2= 2.4.36.3= 2.4.36.4= 2.4.36.5= 2.4.36.6= 2.6= 2.6.18= 2.6.19.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the running kernel versionRun `uname -r` or `cat /proc/version` to identify the installed kernel versionAffected if The kernel version is 2.6.21.7 or lower, or matches any of the specific affected versions (2.2.27, 2.4.36.x, 2.6, 2.6.18, 2.6.19.4)
-
Verify if IPv6 is enabledCheck if the IPv6 module is loaded with `lsmod | grep ipv6` or check for IPv6 interfaces via `cat /proc/net/if_inet6`Affected if IPv6 is loaded or enabled - the vulnerability only affects systems using IPv6 functionality
-
Confirm IPv6 traffic processing capabilityInspect network configuration for active IPv6 addresses or interfaces using `ip -6 addr show` or `ifconfig -a`Affected if The system has IPv6 interfaces or addresses configured, indicating potential exposure to incoming IPv6 packets
-
Identify the kernel source file presenceCheck if the vulnerable file net/ipv6/exthdrs.c exists in the kernel source tree (typically under /usr/src/linux-{version}/net/ipv6/)Affected if The file exists and corresponds to a vulnerable kernel version - indicates the problematic code path is present
The system is affected if it runs a kernel version within the affected range AND has IPv6 enabled, allowing specially crafted IPv6 packets with malformed jumbo payload options to trigger the NULL pointer dereference.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Linux kernel to version 2.6.22 or later, which contains the proper validation fix for the hop-by-hop header handling.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-4567 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data