Linux KernelOperating system · Linux
CVE-2006-3468
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 · uneditedLinux kernel 2.6.x, when using both NFS and EXT3, allows remote attackers to cause a denial of service (file system panic) via a crafted UDP packet with a V2 lookup procedure that specifies a bad file handle (inode number), which triggers an error and causes an exported directory to be remounted read-only.
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 confidenceLinux kernel 2.6.x contains a flaw where a crafted UDP packet with a V2 NFS lookup procedure specifying a bad file handle (inode number) triggers an error that causes an exported EXT3 directory to be remounted read-only, resulting in file system 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.0= 2.6.1= 2.6.2= 2.6.3= 2.6.4= 2.6.5= 2.6.6= 2.6.7= 2.6.8= 2.6.8.1= 2.6.8.1.5= 2.6.9CVSS 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 kernel versionRun 'uname -r' or 'cat /proc/version' to identify the running kernel versionAffected if The kernel version is 2.6.0 through 2.6.9 (exact versions listed in CVE)
-
Verify NFS server is runningRun 'rpcinfo -p' or check for 'nfsd' processes with 'ps aux | grep nfs'Affected if NFS server daemon (nfsd) is running and exporting shares
-
List exported NFS sharesRun 'exportfs -v' or 'showmount -e localhost' to see all exported directoriesAffected if Any directories are exported via NFS
-
Identify filesystem type of exported sharesRun 'mount' or check /etc/fstab and /proc/mounts to determine filesystem types of exported pathsAffected if Any exported NFS share uses the EXT3 filesystem
A system is affected if it runs a Linux kernel from 2.6.0 to 2.6.9, has an NFS server exporting shares, and those exported shares use the EXT3 filesystem - the vulnerability can then be triggered by a crafted UDP packet with a bad file handle.
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 dataApply the appropriate kernel security update for CVE-2006-3468. If immediate patching is not possible, restrict NFS access to trusted hosts via firewall rules or export configuration to reduce attack surface.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3468 — 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 sources- lkml.org
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- support.avaya.com
- www.debian.org
- www.mandriva.com
- www.mandriva.com
- www.novell.com
- www.novell.com
- www.novell.com
- www.novell.com
- www.redhat.com
- www.securityfocus.com
- www.trustix.org
- www.ubuntu.com
- bugzilla.redhat.com
- oval.cisecurity.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-3468 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