cveboard RSS feed

CVE-2025-21855

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2025
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

ibmvnic: Don't reference skb after sending to VIOS

In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Don't reference skb after sending to VIOS Previously, after successfully flushing the xmit buffer to VIOS, the tx_bytes stat was incremented by the length of the skb. It is invalid to access the skb memory after sending the buffer to the VIOS because, at any point after sending, the VIOS can trigger an interrupt to free this memory. A race between reading skb->len and freeing the skb is possible (especially during LPM) and will result in use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ibmvnic_xmit+0x75c/0x1808 [ibmvnic] Read of size 4 at addr c00000024eb48a70 by task hxecom/14495 <...> Call Trace: [c000000118f66cf0] [c0000000018cba6c] dump_stack_lvl+0x84/0xe8 (unreliable) [c000000118f66d20] [c0000000006f0080] print_report+0x1a8/0x7f0 [c000000118f66df0] [c0000000006f08f0] kasan_report+0x128/0x1f8 [c000000118f66f00] [c0000000006f2868] __asan_load4+0xac/0xe0 [c000000118f66f20] [c0080000046eac84] ibmvnic_xmit+0x75c/0x1808 [ibmvnic] [c000000118f67340] [c0000000014be168] dev_hard_start_xmit+0x150/0x358 <...> Freed by task 0: kasan_save_stack+0x34/0x68 kasan_save_track+0x2c/0x50 kasan_save_free_info+0x64/0x108 __kasan_mempool_poison_object+0x148/0x2d4 napi_skb_cache_put+0x5c/0x194 net_tx_action+0x154/0x5b8 handle_softirqs+0x20c/0x60c do_softirq_own_stack+0x6c/0x88 <...> The buggy address belongs to the object at c00000024eb48a00 which belongs to the cache skbuff_head_cache of size 224 ==================================================================

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
032c5e82847a2214c3196a90f0aeba0ce252de58affectedgit501ac6a7e21b82e05207c6b4449812d82820f306UnavailableNone listed
032c5e82847a2214c3196a90f0aeba0ce252de58affectedgit093b0e5c90592773863f300b908b741622eef597UnavailableNone listed
032c5e82847a2214c3196a90f0aeba0ce252de58affectedgit25dddd01dcc8ef3acff964dbb32eeb0d89f098e9UnavailableNone listed
032c5e82847a2214c3196a90f0aeba0ce252de58affectedgitabaff2717470e4b5b7c0c3a90e128b211a23da09UnavailableNone listed
032c5e82847a2214c3196a90f0aeba0ce252de58affectedgitbdf5d13aa05ec314d4385b31ac974d6c7e0997c9UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
4.5affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver4.5UnavailableNone listed
6.1.130unaffectedsemverUnavailable6.1.*None listed
6.6.80unaffectedsemverUnavailable6.6.*None listed
6.12.17unaffectedsemverUnavailable6.12.*None listed
6.13.5unaffectedsemverUnavailable6.13.*None listed
6.14unaffectedoriginal_commit_for_fixUnavailable*None listed