CVE-2016-10905 json
An issue was discovered in fs/gfs2/rgrp.c in the Linux kernel before 4.8.
published 2019-08-19 7 y ago modified 2026-06-17 4 mo ago also EUVD-2016-1899
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
An issue was discovered in fs/gfs2/rgrp.c in the Linux kernel before 4.8. A use-after-free is caused by the functions gfs2_clear_rgrpd and read_rindex_entry.
Patch / fix
- linux linux_kernel 3.16.74, 4.4.191, 4.8
- linux Debian 14, Debian 13, Debian 12 4.8.5-1
debian advisories DEBIAN-CVE-2016-10905
- linux Ubuntu 16.04 LTS 4.4.0-165.193
- linux-aws Ubuntu 16.04 LTS 4.4.0-1095.106
- linux-kvm Ubuntu 16.04 LTS 4.4.0-1059.66
- linux-raspi2 Ubuntu 16.04 LTS 4.4.0-1123.132
- linux-snapdragon Ubuntu 16.04 LTS 4.4.0-1127.135
- linux-snapdragon Ubuntu 18.04 LTS 4.15.0-1053.57
- linux-aws Ubuntu Pro 14.04 LTS 4.4.0-1055.59
- linux-fips Ubuntu Pro FIPS-updates 16.04 LTS 4.4.0-1022.27
ubuntu advisories UBUNTU-CVE-2016-10905
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-syms SLES for SAP 12 SP3, SLES 12 SP3-LTSS, SLES 12 SP3-BCL +3 more 4.4.180-94.156.1
- kernel-source SLES for SAP 12 SP3, SLES 12 SP3-LTSS, SLES 12 SP3-BCL +3 more 4.4.180-94.156.1
- kernel-default SLES for SAP 12 SP3, SLES 12 SP3-LTSS, SLES 12 SP3-BCL +4 more 4.4.180-94.156.1
- kgraft-patch-SLE12-SP3_Update_43 SLES for SAP 12 SP3, SLES 12 SP3-LTSS, OpenStack Cloud Crowbar 8 +2 more 1-4.3.1
- kernel-syms SLES 12 SP2-BCL 4.4.121-92.169.1
- kernel-source SLES 12 SP2-BCL 4.4.121-92.169.1
- kernel-default SLES 12 SP2-BCL 4.4.121-92.169.1
suse advisories SUSE-SU-2022:0762-1SUSE-SU-2022:0756-1
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-2016-10905 updated cvss 6.2
kernel: use-after-free in fs/gfs2/rgrp.c
-
Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, kernel-alt, python-perf, +9 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmwarenot affected: vulnerable code not present
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.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.1 | AV:L/AC:L/Au:N/C:P/I:P/A:C |
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=36e4ad0316c017d5b271378ed9a1c9a4b77fab5f
patch, vendor-advisory
-
usn.ubuntu.com
/4145-1/
vendor-advisory, vdb-entry
-
lists.debian.org
/debian-lts-announce/2019/09/msg00025.html
mailing-list, vendor-advisory
-
support.f5.com
/csp/article/K31332013
third-party-advisory, vdb-entry
- support.f5.com /csp/article/K31332013?utm_source=f5support&%3Butm_medium=RSS
-
packetstormsecurity.com
/files/154951/Kernel-Live-Patch-Security-Notice-LSN-0058-1.html
third-party-advisory, vdb-entry
-
seclists.org
/bugtraq/2019/Nov/11
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/155212/Slackware-Security-Advisory-Slackware-14.2-kernel-Updates.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2016-10905
- NVD CVE-2016-10905
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.