Skip to content
Fencer Vulns
critical 9.3

CVE-2008-3915 in the critical feed json

Buffer overflow in nfsd in the Linux kernel before 2.6.26.4, when NFSv4 is enabled, allows remote attackers to have an unknown impact via v…

published 2008-09-09 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3900

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.4%
EPSS 4.4% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

Buffer overflow in nfsd in the Linux kernel before 2.6.26.4, when NFSv4 is enabled, allows remote attackers to have an unknown impact via vectors related to decoding an NFSv4 acl.

Patch / fix

  • kernel-rt enterprise mrg 1 2.6.24.7-81.el5rt
  • kernel-rt-trace enterprise mrg 1 2.6.24.7-81.el5rt
  • kernel-rt-vanilla enterprise mrg 1 2.6.24.7-81.el5rt
  • kernel-rt-debuginfo-common enterprise mrg 1 2.6.24.7-81.el5rt

red hat advisories RHSA-2008:0857

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2008-3915 updated

kernel: nfsd: fix buffer overrun decoding NFSv4 acl

  • Red Hat MRG Realtime for RHEL 5 Server kernel-rt 2.6.24.7-81.el5rt, kernel-rt-trace 2.6.24.7-81.el5rt, kernel-rt-vanilla 2.6.24.7-81.el5rt, kernel-rt-debuginfo-common 2.6.24.7-81.el5rt
    fixed: vendor fix RHSA-2008:0857

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.35% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Technology feeds

References

Sources

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.