Skip to content
Fencer Intel
medium 4.9

CVE-2010-4165 json

The do_tcp_setsockopt function in net/ipv4/tcp.c in the Linux kernel before 2.6.37-rc2 does not properly restrict TCP_MAXSEG (aka MSS) valu…

published 15y ago modified 4mo ago also EUVD-2010-4141

cvss
4.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
2
Exploit-DB

Summary

The do_tcp_setsockopt function in net/ipv4/tcp.c in the Linux kernel before 2.6.37-rc2 does not properly restrict TCP_MAXSEG (aka MSS) values, which allows local users to cause a denial of service (OOPS) via a setsockopt call that specifies a small value, leading to a divide-by-zero error or incorrect use of a signed integer.

Patch / fix

  • linux linux_kernel 2.6.37
  • kernel-rt enterprise mrg 1 2.6.33.7-rt29.55.el5rt
  • perf enterprise mrg 1 2.6.33.7-rt29.55.el5rt
  • kernel-rt-trace enterprise mrg 1 2.6.33.7-rt29.55.el5rt
  • kernel-rt-vanilla enterprise mrg 1 2.6.33.7-rt29.55.el5rt
  • kernel-rt-debuginfo-common enterprise mrg 1 2.6.33.7-rt29.55.el5rt
  • kernel RHEL 6 2.6.32-71.18.1.el6
  • perf RHEL 6 2.6.32-71.18.1.el6
  • kernel-kdump RHEL 6 2.6.32-71.18.1.el6

red hat advisories RHSA-2011:0330RHSA-2011:0283

Is CVE-2010-4165 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2010-4165 updated cvss 4.9

kernel: possible kernel oops from user MSS

  • Red Hat MRG Realtime for RHEL 5 Server perf 2.6.33.7-rt29.55.el5rt, kernel-rt 2.6.33.7-rt29.55.el5rt, kernel-rt-trace 2.6.33.7-rt29.55.el5rt, kernel-rt-vanilla 2.6.33.7-rt29.55.el5rt, kernel-rt-debuginfo-common 2.6.33.7-rt29.55.el5rt
    fixed: vendor fix RHSA-2011:0330
  • Red Hat Enterprise Linux Desktop (v. 6) perf 2.6.32-71.18.1.el6, kernel 2.6.32-71.18.1.el6, kernel-kdump 2.6.32-71.18.1.el6, kernel-firmware 2.6.32-71.18.1.el6, kernel-bootwrapper 2.6.32-71.18.1.el6, kernel-debuginfo-common-i686 2.6.32-71.18.1.el6, +3 more Red Hat Enterprise Linux HPC Node (v. 6) perf 2.6.32-71.18.1.el6, kernel 2.6.32-71.18.1.el6, kernel-kdump 2.6.32-71.18.1.el6, kernel-firmware 2.6.32-71.18.1.el6, kernel-bootwrapper 2.6.32-71.18.1.el6, kernel-debuginfo-common-i686 2.6.32-71.18.1.el6, +3 more Red Hat Enterprise Linux Server (v. 6) perf 2.6.32-71.18.1.el6, kernel 2.6.32-71.18.1.el6, kernel-kdump 2.6.32-71.18.1.el6, kernel-firmware 2.6.32-71.18.1.el6, kernel-bootwrapper 2.6.32-71.18.1.el6, kernel-debuginfo-common-i686 2.6.32-71.18.1.el6, +3 more Red Hat Enterprise Linux Workstation (v. 6) perf 2.6.32-71.18.1.el6, kernel 2.6.32-71.18.1.el6, kernel-kdump 2.6.32-71.18.1.el6, kernel-firmware 2.6.32-71.18.1.el6, kernel-bootwrapper 2.6.32-71.18.1.el6, kernel-debuginfo-common-i686 2.6.32-71.18.1.el6, +3 more
    fixed: vendor fix RHSA-2011:0283

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

Timeline

  1. Published
  2. First public exploit (EDB-16263)

Exploit prediction

1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-16952 Linux Kernel < 2.6.37-rc2 - 'TCP_MAXSEG' Kernel Panic (Denial of Service) (2) dos, 2011-03-10
  • EDB-16263 Linux Kernel 2.6.37 - Local Kernel Denial of Service (1) dos, 2011-03-02
  • securityreason.com http://securityreason.com/securityalert/8111 referenced PoC, tagged "exploit" by a source, unverified
  • securityreason.com http://securityreason.com/securityalert/8123 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel 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.