Skip to content
Fencer Intel
high 7.2

CVE-2010-1162 json

The release_one_tty function in drivers/char/tty_io.c in the Linux kernel before 2.6.34-rc4 omits certain required calls to the put_pid fun…

published 16y ago modified 4mo ago also EUVD-2010-1192

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

Summary

The release_one_tty function in drivers/char/tty_io.c in the Linux kernel before 2.6.34-rc4 omits certain required calls to the put_pid function, which has unspecified impact and local attack vectors.

Patch / fix

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

red hat advisories RHSA-2010:0631

Is CVE-2010-1162 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-1162 updated cvss 4.9

kernel: tty: release_one_tty() forgets to put pids

  • Red Hat MRG Realtime for RHEL 5 Server kernel-rt 2.6.24.7-161.el5rt, kernel-rt-trace 2.6.24.7-161.el5rt, kernel-rt-vanilla 2.6.24.7-161.el5rt, kernel-rt-firmware 2.6.24.7-161.el5rt, kernel-rt-debuginfo-common 2.6.24.7-161.el5rt
    fixed: vendor fix RHSA-2010:0631

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

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

CVSS scores

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

Classification

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.