Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64190net: team: fix NULL pointer dereference in team_xmit during mode change

Description

In the Linux kernel, the following vulnerability has been resolved: net: team: fix NULL pointer dereference in team_xmit during mode change __team_change_mode() clears team->ops with memset() before restoring safe dummy handlers via team_adjust_ops(). A concurrent team_xmit() running under RCU on another CPU can read team->ops.transmit during this window and call a NULL function pointer, crashing the kernel. The race requires a mode change (CAP_NET_ADMIN) concurrent with transmit on the team device. BUG: kernel NULL pointer dereference, address: 0000000000000000 Oops: 0010 [#1] SMP KASAN NOPTI RIP: 0010:0x0 Call Trace: team_xmit (drivers/net/team/team_core.c:1853) dev_hard_start_xmit (net/core/dev.c:3904) __dev_queue_xmit (net/core/dev.c:4871) packet_sendmsg (net/packet/af_packet.c:3109) __sys_sendto (net/socket.c:2265) The original code assumed that no ports means no traffic, so mode changes could freely memset()/memcpy() the ops. AF_PACKET with forced carrier breaks that assumption. Prevent the race instead of making it safe: replace memset()/memcpy() with per-field updates that never touch transmit or receive. Those two handlers are managed solely by team_adjust_ops(), which already installs dummies when tx_en_port_count == 0 (always true during mode change since no ports are present). WRITE_ONCE/READ_ONCE prevent store/load tearing on the handler pointers. synchronize_net() before exit_op() drains in-flight readers that may still reference old mode state from before port removal switched the handlers to dummies.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64190, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – < d61bf3bc17de1e18cbdac94cf5389bb9dc2ddfe7
    • affected 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – < ac342f86638f5e184c8511cff12a421aea56acc6
    • affected 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – < a879f78c478cee77f4bd43e92225a640c23f45d4
    • affected 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – < 9486377e5e971988a3add171c398eb654a866fab
    • affected 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – < cde5c7f0286c4203d0abc7248201542aa8bf33bb
    • affected 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – < 03e9405c518c4d61f28079492f252d6d4e2bac5c
    • affected 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – < 25fe708bbc59289d3d1ea4b126fbc1b460a072a5
  • Linux · Linux

    • affected 3.3
    • unaffected < 3.3
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.1 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64190 badge
[![CVE-2026-64190](https://cveledger.app/badge/CVE-2026-64190.svg)](https://cveledger.app/cve/CVE-2026-64190)

Record last updated .