Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 7565d4df66b6619b50dc36618d8b8f1787d77e19, ba0c7fff6616025a7d3a9e887e7ce16b06dc34b9, fc6f36eaaedcf4b81af6fe1a568f018ffd530660.

Low priority for now. Upgrade to Linux Linux 7565d4df66b6619b50dc36618d8b8f1787d77e19, ba0c7fff6616025a7d3a9e887e7ce16b06dc34b9, fc6f36eaaedcf4b81af6fe1a568f018ffd530660 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ice: Fix PTP NULL pointer dereference during VSI rebuild Fix race condition where PTP periodic work runs while VSI is being rebuilt, accessing NULL vsi->rx_rings. The sequence was: 1. ice_ptp_prepare_for_reset() cancels PTP work 2. ice_ptp_rebuild() immediately queues PTP work 3. VSI rebuild happens AFTER ice_ptp_rebuild() 4. PTP work runs and accesses NULL vsi->rx_rings Fix: Keep PTP work cancelled during rebuild, only queue it after VSI rebuild completes in ice_rebuild(). Added ice_ptp_queue_work() helper function to encapsulate the logic for queuing PTP work, ensuring it's only queued when PTP is supported and the state is ICE_PTP_READY. Error log: [ 121.392544] ice 0000:60:00.1: PTP reset successful [ 121.392692] BUG: kernel NULL pointer dereference, address: 0000000000000000 [ 121.392712] #PF: supervisor read access in kernel mode [ 121.392720] #PF: error_code(0x0000) - not-present page [ 121.392727] PGD 0 [ 121.392734] Oops: Oops: 0000 [#1] SMP NOPTI [ 121.392746] CPU: 8 UID: 0 PID: 1005 Comm: ice-ptp-0000:60 Tainted: G S 6.19.0-rc6+ #4 PREEMPT(voluntary) [ 121.392761] Tainted: [S]=CPU_OUT_OF_SPEC [ 121.392773] RIP: 0010:ice_ptp_update_cached_phctime+0xbf/0x150 [ice] [ 121.393042] Call Trace: [ 121.393047] <TASK> [ 121.393055] ice_ptp_periodic_work+0x69/0x180 [ice] [ 121.393202] kthread_worker_fn+0xa2/0x260 [ 121.393216] ? __pfx_ice_ptp_periodic_work+0x10/0x10 [ice] [ 121.393359] ? __pfx_kthread_worker_fn+0x10/0x10 [ 121.393371] kthread+0x10d/0x230 [ 121.393382] ? __pfx_kthread+0x10/0x10 [ 121.393393] ret_from_fork+0x273/0x2b0 [ 121.393407] ? __pfx_kthread+0x10/0x10 [ 121.393417] ret_from_fork_asm+0x1a/0x30 [ 121.393432] </TASK>

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Feb 14, 2026
Updated
Oct 19, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23210

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.9 and later · before 6.18.10
  • linux linux kernel6.19

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.9affected
    • 803bef817807d2d36c930dada20c96fffae0dd19 and later · before ba0c7fff6616025a7d3a9e887e7ce16b06dc34b9affected · git
    • 803bef817807d2d36c930dada20c96fffae0dd19 and later · before 7565d4df66b6619b50dc36618d8b8f1787d77e19affected · git
    • 803bef817807d2d36c930dada20c96fffae0dd19 and later · before fc6f36eaaedcf4b81af6fe1a568f018ffd530660affected · git
    • before 6.9not affected · semver
    • 6.12.80 and later · up to and including 6.12.*not affected · semver
    • 6.18.10 and later · up to and including 6.18.*not affected · semver
    • 6.19 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-23208Feb 14, 2026 · ALSA: usb-audio: Prevent excessive number of frames
    31Monitor
  • ← EarlierCVE-2026-23209Feb 14, 2026 · macvlan: fix error recovery in macvlan_common_newlink()
    31Monitor
  • Later →CVE-2026-23211Feb 18, 2026 · mm, swap: restore swap_space attr aviod kernel panic
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux7565d4df66b6619b50dc36618d8b8f1787d77e19Vendor (CNA)
Linux Linuxba0c7fff6616025a7d3a9e887e7ce16b06dc34b9Vendor (CNA)
Linux Linuxfc6f36eaaedcf4b81af6fe1a568f018ffd530660Vendor (CNA)
almalinux:kernel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.85-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-55.76.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
rocky linux:kernel0:5.14.0-611.47.1.el9_7 · Rocky Linux:9Package registry (OSV)
suse:kernel-64kb6.4.0-150700.53.81.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)

+11

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records