How many CVEs have patched do_check?

7 published CVEs changed do_check in torvalds/linux, in 15 distinct patches totalling 40 changed lines, between 2017 and 2025.

What is the latest CVE that changed do_check?

CVE-2022-50650 (bpf: Fix reference state management for synchronous callbacks), published 2025-12-09, changed lines 12358 to 12377 of kernel/bpf/verifier.c.

How does do_check compare to the rest of torvalds/linux?

torvalds/linux has 19,281 CVEs with a located fix in total; 7 of them changed do_check.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

torvalds/linux

Function

do_check

Name: do_check in torvalds/linux: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

kernel/bpf/verifier.c

Last patched December 9, 2025

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2017–2025

Years

By CVE publication date

Overview

do_check in torvalds/linux was changed by 7 published CVE fixes between 2017 and 2025, in 15 distinct patches that added or removed 40 lines in total.

torvalds/linux has 19,281 CVEs with a located fix in total, so 0% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed do_check, newest first, with the lines each fix touched.

bpf: Fix reference state management for synchronous callbacks
CVE-2022-50650 · lines 12358–12377 · +10 −4 in 2 hunks
High · CVSS 7.8
EPSS 0.2%2025-12-09
bpf: copy_verifier_state() should copy 'loop_entry' field
CVE-2025-38060 · lines 18724–18725 · +2 −0
High · CVSS 7.8
EPSS 0.2%2025-06-18
bpf: support non-r10 register spill/fill to/from stack in precision tracking
CVE-2023-52920 · lines 17098–17140 · +4 −1 in 2 hunks
High · CVSS 7.8
EPSS 0.3%2024-11-05
CVE-2022-0500
CVE-2022-0500 · line 11412 · +1 −1
High · CVSS 7.8
EPSS 0.4%2022-03-25
CVE-2019-7308
CVE-2019-7308 · lines 5820–5883 · +9 −4 in 3 hunks
Medium · CVSS 5.6
EPSS 0.5%2019-02-01
CVE-2017-17862
CVE-2017-17862 · lines 3830–4026 · +2 −0 in 2 hunks
Medium · CVSS 5.5
EPSS 0.4%2017-12-23
CVE-2017-9150
CVE-2017-9150 · line 2867 · +1 −1
Medium · CVSS 5.5
EPSS 1.3%2017-05-22

Get an alert when the next CVE fix lands in torvalds/linux, with the patched functions.

Monitor linux CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in torvalds/linux changed by the most CVE fixes.

smb2_sess_setup13 CVEs · fs/smb/server/smb2pdu.c adjust_ptr_min_max_vals13 CVEs · kernel/bpf/verifier.c ext4_fill_super13 CVEs · fs/ext4/super.c bcm_rx_setup12 CVEs · net/can/bcm.c copy_process12 CVEs · kernel/fork.c smb2_sess_setup11 CVEs · fs/ksmbd/smb2pdu.c

All patched functions in torvalds/linux

Frequently asked questions

Common questions about CVE fixes to do_check.

How many CVEs have patched do_check?: 7 published CVEs changed do_check in torvalds/linux, in 15 distinct patches totalling 40 changed lines, between 2017 and 2025.
What is the latest CVE that changed do_check?: CVE-2022-50650 (bpf: Fix reference state management for synchronous callbacks), published 2025-12-09, changed lines 12358 to 12377 of kernel/bpf/verifier.c.
How does do_check compare to the rest of torvalds/linux?: torvalds/linux has 19,281 CVEs with a located fix in total; 7 of them changed do_check.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track torvalds/linux CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing