# CVE-2016-4913: Information disclosure in n/a

> Local attackers can read sensitive kernel memory via a crafted ISO9660 filesystem due to improper handling of null characters in Rock Ridge entries.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-4913, GHSA-9vmv-j366-j2m2, UBUNTU-CVE-2016-4913

## What is CVE-2016-4913?

CVE-2016-4913 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 23 May 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The get_rock_ridge_filename function in fs/isofs/rock.c in the Linux kernel before 4.5.5 mishandles NM (aka alternate name) entries containing \0 characters, which allows local users to obtain sensitive information from kernel memory or possibly have unspecified other impact via a crafted isofs filesystem.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-4913?

It affects 6 products.


Products: Canonical Ubuntu Linux, Linux kernel, Novell Suse Linux Enterprise Debuginfo, Novell Suse Linux Enterprise Server, Novell Suse Linux Enterprise Software Development Kit, Oracle Linux.

## How do I fix CVE-2016-4913?

Apply the vendor's patch.

## Is CVE-2016-4913 being exploited?

There is no known exploitation of CVE-2016-4913 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4913 and fix it if it is affected.

What it is: CVE-2016-4913 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 23 May 2016. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-4913 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-4913/ (Markdown: https://insights.sbomify.com/CVE-2016-4913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-4913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-4913
- OSV: https://osv.dev/vulnerability/CVE-2016-4913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-4913/
Summaries are generated and may contain mistakes; the official description above is the record.