# printk: Fix signed integer overflow when defining LOG_BUF_LEN_MAX

CVE record · `CVE-2024-58017`

- **Identifiers:** `CVE-2024-58017`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 Feb 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 Feb 2025, 02:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `e6fe3e5b7d16e8f146a4ae7fe481bc6e97acde1e to before 54c14022fa2ba427dc543455c2cf9225903a7174` (git)
  - affected: `e6fe3e5b7d16e8f146a4ae7fe481bc6e97acde1e to before dfb7b179741ee09506dc7719d92f9e1cea01f10e` (git)
  - affected: `e6fe3e5b7d16e8f146a4ae7fe481bc6e97acde1e to before bb8ff054e19fe27f4e5eaac1b05e462894cfe9b1` (git)
  - affected: `e6fe3e5b7d16e8f146a4ae7fe481bc6e97acde1e to before 9a6d43844de2479a3ff8d674c3e2a16172e01598` (git)
  - affected: `e6fe3e5b7d16e8f146a4ae7fe481bc6e97acde1e to before 4acf6bab775dbd22a9a799030a808a7305e01d63` (git)
  - affected: `e6fe3e5b7d16e8f146a4ae7fe481bc6e97acde1e to before 404e5fd918a0b14abec06c7eca128f04c9b98e41` (git)
  - affected: `e6fe3e5b7d16e8f146a4ae7fe481bc6e97acde1e to before 4a2c4e7265b8eed83c25d86d702cea06493cab18` (git)
  - affected: `e6fe3e5b7d16e8f146a4ae7fe481bc6e97acde1e to before 3d6f83df8ff2d5de84b50377e4f0d45e25311c7a` (git)
  - affected: `55b2c1ccb82143be1ed9e1922976dbe63917fe68` (git)
  - affected: `089d475a4cdb5848998b3cb37e545413ed054784` (git)
  - affected: `695583334b6b7f82c39ee124edfbfa48145ed571` (git)
  - affected: `3404019d6d0f4c0108b77d44e97e2e39ca937e6f` (git)
  - and 4 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.20`
  - unaffected: `before 4.20` (semver)
  - unaffected: `5.4.291 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.235 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.179 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.129 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.78 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.14 to 6.12.*, inclusive` (semver)
  - unaffected: `6.13.3 to 6.13.*, inclusive` (semver)
  - unaffected: `6.14 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 17th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 27 Feb 2025, 02:12 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2024-58017)
- 27 Feb 2025, 03:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2024-58017)

## Sources

- [CVE List: CVE-2024-58017](https://www.cve.org/CVERecord?id=CVE-2024-58017)
- [NVD: CVE-2024-58017](https://nvd.nist.gov/vuln/detail/CVE-2024-58017)

### References from the CNA

- <https://git.kernel.org/stable/c/54c14022fa2ba427dc543455c2cf9225903a7174>
- <https://git.kernel.org/stable/c/dfb7b179741ee09506dc7719d92f9e1cea01f10e>
- <https://git.kernel.org/stable/c/bb8ff054e19fe27f4e5eaac1b05e462894cfe9b1>
- <https://git.kernel.org/stable/c/9a6d43844de2479a3ff8d674c3e2a16172e01598>
- <https://git.kernel.org/stable/c/4acf6bab775dbd22a9a799030a808a7305e01d63>
- <https://git.kernel.org/stable/c/404e5fd918a0b14abec06c7eca128f04c9b98e41>
- <https://git.kernel.org/stable/c/4a2c4e7265b8eed83c25d86d702cea06493cab18>
- <https://git.kernel.org/stable/c/3d6f83df8ff2d5de84b50377e4f0d45e25311c7a>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2024-58017>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2024-58017/>. Everything for agents: <https://agentprime.io/llms.txt>.
