CVE-2011-3191: Integer signedness error in the CIFSFindNext function in fs/cifs/cifssmb.c in the Linux kernel before 3.1 allows remote CIFS servers to…
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 65.2% of all records.
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: linux-2.6 (Debian:5.0) 2.6.26-26lenny4; linux-2.6 (Debian:6.0) 2.6.32-35squeeze1; kernel (Red Hat:enterprise_linux:5::client) 0:2.6.18-274.7.1.el5.
Low priority for now. Upgrade to linux-2.6 (Debian:5.0) 2.6.26-26lenny4; linux-2.6 (Debian:6.0) 2.6.32-35squeeze1; kernel (Red Hat:enterprise_linux:5::client) 0:2.6.18-274.7.1.el5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Integer signedness error in the CIFSFindNext function in fs/cifs/cifssmb.c in the Linux kernel before 3.1 allows remote CIFS servers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a large length value in a response to a read request for a directory.
- Published
- May 24, 2012
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- CWE-119
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 3.0.5
- redhat enterprise linux4.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:5.0 | linux-2.6 | before 2.6.26-26lenny4 | 2.6.26-26lenny4 |
| Debian:6.0 | linux-2.6 | before 2.6.32-35squeeze1 | 2.6.32-35squeeze1 |
| Red Hat:enterprise_linux:5::client | kernel | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debug | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debug-debuginfo | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debug-devel | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debuginfo | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-debuginfo-common | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-devel | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-doc | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-PAE | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-PAE-debuginfo | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-PAE-devel | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-xen | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-xen-debuginfo | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::client | kernel-xen-devel | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::server | kernel-kdump | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::server | kernel-kdump-debuginfo | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:5::server | kernel-kdump-devel | before 0:2.6.18-274.7.1.el5 | 0:2.6.18-274.7.1.el5 |
| Red Hat:enterprise_linux:6::server | kernel | before 0:2.6.32-131.21.1.el6 | 0:2.6.32-131.21.1.el6 |
| Red Hat:enterprise_linux:6::server | kernel-bootwrapper | before 0:2.6.32-131.21.1.el6 | 0:2.6.32-131.21.1.el6 |
| Red Hat:enterprise_linux:6::server | kernel-debug | before 0:2.6.32-131.21.1.el6 | 0:2.6.32-131.21.1.el6 |
| Red Hat:enterprise_linux:6::server | kernel-debug-debuginfo | before 0:2.6.32-131.21.1.el6 | 0:2.6.32-131.21.1.el6 |
| Red Hat:enterprise_linux:6::server | kernel-debug-devel | before 0:2.6.32-131.21.1.el6 | 0:2.6.32-131.21.1.el6 |
+29
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2011-2918May 24, 2012 · The Performance Events subsystem in the Linux kernel before 3.1 does not properly handle event overflows associated with…22Monitor
- ← EarlierCVE-2011-3188May 24, 2012 · The (1) IPv4 and (2) IPv6 implementations in the Linux kernel before 3.1 use a modified MD4 algorithm to generate sequence numbers and…38Monitor
- Later →CVE-2011-3353May 24, 2012 · Buffer overflow in the fuse_notify_inval_entry function in fs/fuse/dev.c in the Linux kernel before 3.1 allows local users to cause a…22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:linux-2.6 | 2.6.32-35squeeze1 · Debian:6.0 | Package registry (OSV) |
| red hat:kernel | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debug | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-debuginfo-common | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-devel | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-doc | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-PAE | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-PAE-debuginfo | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-PAE-devel | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:kernel-xen | 0:2.6.18-274.7.1.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.