Safeguard
Vulnerability Analysis•

CVE-2021-3600: High eBPF Bounds Bug in the Linux Kernel

CVE-2021-3600 is a high local eBPF verifier flaw in the Linux kernel. Install your distribution's kernel update that cites this CVE and reboot.

Safeguard Security Team
3 min read

CVE-2021-3600 is a high severity (CVSS 7.8) flaw in the Linux kernel eBPF verifier, which did not track bounds for 32 bit registers during div and mod operations. A local attacker could possibly execute arbitrary code. Update to a kernel that includes the upstream fix commit e88b2c6e5a4d.

What's affected

  • The Linux kernel, with the eBPF verifier's 32 bit div and mod handling, per the record.
  • Fixed: upstream commit e88b2c6e5a4d9ce30d75391e4d950da74bb2bd90. Ubuntu's notice USN-5003-1 covers its kernels, but I could not retrieve it, so confirm exact package versions there or with your distribution.

The record scores it 7.8 (High) with vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.

How to check if you're exposed

Run uname -r to see the running kernel, then check your distribution's security tracker for this CVE. Also check whether unprivileged eBPF is disabled with sysctl kernel.unprivileged_bpf_disabled.

What to do now

  1. Check distribution advisories for CVE-2021-3600.
  2. Install the updated kernel package.
  3. Reboot into it and confirm with uname -r.
  4. Consider disabling unprivileged eBPF where you do not need it.
  5. For containers, remember they share the host kernel.

After you patch, record the new version for Linux kernel eBPF in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.

Why it matters

The record maps the flaw to CWE-125, out of bounds read, and CWE-787, out of bounds write. The eBPF verifier checks programs before they run in the kernel. If it loses track of value bounds, a program it approved can access memory it should not.

Because the attacker has to be local, the main risk is escalation after another compromise, or from a container on a shared host. Kernel updates need a reboot, so plan for it.

To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Do containers protect me?

No. Containers share the host kernel, so a kernel flaw is a host level issue.

How do I find every place Linux kernel eBPF is used?

Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.