Skip to content
statance
MenuClose
unknown

CVE-2026-99232

tracing/syscalls: Use copy_from_user for the faultable syscall buffer

Published 2 Nov 2026 · Source updated 3 Nov 2026 · Retrieved 2026-11-05 12:07 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

In the Linux kernel, the following vulnerability has been resolved:

tracing/syscalls: Use copy_from_user for the faultable syscall buffer

syscall_copy_user_array() copies the buffer argument of faultable syscalls (write, pwrite64, ...) with __copy_from_user(), which skips access_ok(). Use copy_from_user() instead so a non-user address is rejected and the entry is recorded as faulted.

It could be a security concern for machines that trust perf a bit too much.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: baa031b7bd2ce7502339174a42974321859ecd6a to < e33e2718c62a602001ab549642a1aed0be797105; affected: baa031b7bd2ce7502339174a42974321859ecd6a to < 041d1a568a11a7ed7415ef1408d0c65041c1ad69; affected: baa031b7bd2ce7502339174a42974321859ecd6a to < 097fd0050089df17b032f2b852b9b65e548e342aSee vendor advisory
LinuxLinuxaffected: 6.19; unaffected: 0 to < 6.19; unaffected: 7.2.14 to ≤ 7.2.*; unaffected: 7.3.1 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed