OESA-2026-4898: kernel security update

Published Nov 19, 2026
·
Updated

The Linux Kernel, the operating system core itself. Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

usb: typec: wcove: don't write past struct pdmessage in wcovereadrxbuffer()

wcovereadrxbuffer() copies the PD RX FIFO into the caller's struct pdmessage with

for (i = 0; i < USBCRXINFORXBYTES(info); i++) regmapread(wcove->regmap, USBCRXDATA + i, msg + i);

which has two problems:

USBCRXINFORXBYTES() is a 5-bit field (max 31) while struct pdmessage is 30 bytes (le16 header + le32 payload[PDMAXPAYLOAD], packed). The byte count latched in RXINFO is the number of bytes the port partner put on the wire, so a malicious partner that transmits a 31-byte frame can drive the loop one byte past the destination if the WCOVE BMC receiver does not enforce the PD object-count limit in hardware. The existing FIXME flagged this as unverified.

Independently, regmapread() takes an unsigned int and stores a full unsigned int at the destination. Passing the byte pointer msg + i means each iteration writes four bytes; the high three are zero (valbits is 8) and are normally overwritten by the next iteration, but the final iteration's high bytes are not. With RXBYTES == 30 the i == 29 iteration already writes three zero bytes past msg, which sits on the IRQ thread's stack in wcovetypecirq().

Clamp the loop to sizeof(struct pdmessage) and read each register into a local before storing only its low byte, so the copy can never exceed the destination regardless of what RXINFO reports.(CVE-2026-63960)

In the Linux kernel, the following vulnerability has been resolved:

dm-verity: fix buffer overflow in FEC calculation

There's a buffer overflow in dm-verity-fec:

if (neras && neras <= v->fec->roots) fio->erasures[(neras)++] = i;

This allows neras to reach roots + 1 (the post-increment pushes it past roots). This value is then passed as noeras to decoders8(). Inside the RS decoder (lib/reedsolomon/decoders.c:113-121), the erasure locator polynomial loop writes lambda[j] where j can reach nroots + 1 — one element past the end of lambda[] (which is sized nroots + 1, valid indices 0..nroots). The out-of-bounds write lands on syn[0], corrupting the syndrome buffer.(CVE-2026-72098)

In the Linux kernel, the following vulnerability has been resolved:

net/x25: fix use-after-free of the socket by its timers

The x25 timers are armed with modtimer() and cancelled with timerdelete(), so a pending timer holds no reference on the socket and a cancel does not wait for a callback already running on another CPU.

x25heartbeatexpiry() also rearms unconditionally, so it can reinstall sk->sktimer after x25destroysocket() has passed its cancel point. The following sockput() frees the socket while the timer is still queued, and the next expiry uses freed memory. KASAN reports a slab-use-after-free on the kmalloc-2k object freed by close().

timerdeletesync() cannot be used here: x25heartbeatexpiry() and x25timerexpiry() both reach the cancels from inside the timer they would wait on, through x25destroysocket() and x25disconnect().

Arm the timers with skresettimer() and cancel them with skstoptimer() so that an armed timer owns a reference, and release it in both expiry handlers. Rearm the heartbeat only while skhashed(sk) is still true, since x25destroysocket() unlinks the socket before dropping it. Arm the deferred destroy timer the same way and drop its reference in x25destroytimer().

Reproduced on net with KASAN, with the heartbeat period shortened so the window recurs. With this patch the reproducer no longer triggers a report and /proc/net/x25 drains.

Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>(CVE-2026-74628)

In the Linux kernel, the following vulnerability has been resolved:

net: prestera: validate firmware header length

presterafwhdrparse() reads the firmware header before checking that the firmware image contains that header.

Reject images shorter than struct presterafwheader before decoding the magic and version fields.(CVE-2026-74693)

In the Linux kernel, the following vulnerability has been resolved:

kcov: fix data corruption and race conditions on PREEMPTRT

syzbot is reporting KCOV state corruption on PREEMPTRT kernels, for the temporary storage used for saving/restoring remote KCOV state is currently allocated as the per-CPU area.

On PREEMPTRT kernels, softirq handlers run as preemptible task threads (e.g., ksoftirqd). If a softirq context preempts a task running a remote KCOV session, it safely saves the task's state into the per-CPU area. However, if that softirq thread is subsequently preempted by a higher- priority softirq thread on the same CPU, the second softirq will overwrite the same per-CPU area, permanently destroying the original task's KCOV state.

Fix this data corruption by moving the temporary storage from the per-CPU area to the per-thread area. Since each softirq thread now owns its own task context, nested softirq preemption no longer causes data overwrites.

Note that while the temporary storage is now on a per-thread basis, the per-CPU kcovpercpudata.lock must be retained, for we need to ensure that kcovremotestart() and kcovremotestop() operate atomically without racing against asynchronous interrupts that manipulate the current task's KCOV state.

It is likely that GFPKERNEL allocation by vmallocnode() in kcovinit() has already called panic() before returning NULL, for there will be no OOM-killable userspace processes when init function of built-in module runs. But this patch also fixes crashing the kernel when vmallocnode() in kcovinit() returned NULL, for kcovinit() left per-CPU irqarea == NULL but kcovremotestart() depends on per-CPU irqarea != NULL, resulting in

(1) doing vmalloc() in kcovremotestart() despite !intask() context

(2) out-of-array-bounds access if (1) succeeded but kcov->remotesize < CONFIGKCOVIRQAREASIZE

(3) always leak memory allocated by (1), eventually killing all OOM-killable userspace processes

problems.(CVE-2026-80916)

In the Linux kernel, the following vulnerability has been resolved:

ALSA: harmony: initialize locks before requesting IRQ

sndharmonycreate() registers the IRQ before initializing h->lock and h->mixerlock. A pending interrupt can invoke the handler while these locks are uninitialized.

Initialize both locks before requesting the IRQ so the handler always sees valid lock state.(CVE-2026-89980)

In the Linux kernel, the following vulnerability has been resolved:

ALSA: usb-audio: fix OOB write in sndusbmidius122loutput()

The sndusbmidius122loutput() picks a count of 2 on anything slower than high speed and never relates it to ep->maxtransfer. The URB buffer holds exactly maxtransfer bytes, so a device declaring a one byte bulk endpoint takes two bytes from sndrawmiditransmit(), and the memset that pads the rest computes 1 - 2 in int and wraps to SIZEMAX.

Only 0x800e and 0x800f are pinned to nine bytes. The US-122MKII at 0x0644:0x8021 falls to the default and takes usbmaxpacket(), which the USB core only clamps downward.

The akai and novation output ops in this file were given the same guard recently. Do the same here.(CVE-2026-90033)

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix slab-out-of-bounds read in ksmbdallocuser()

ksmbdallocuser() copies resp->hashsz bytes out of the mountd IPC login response with

user->passkeysz = resp->hashsz; user->passkey = kmalloc(resp->hashsz, KSMBDDEFAULTGFP); if (user->passkey) memcpy(user->passkey, resp->hash, resp->hashsz);

resp->hashsz is a u16 supplied by the response, but resp->hash[] is only KSMBDREQMAXHASHSZ bytes. A malformed or malicious login response can set hashsz well beyond that (up to 65535), so the memcpy() reads past the end of the response object. ipcvalidatemsg() does not bound hashsz, so reject any response whose hashsz exceeds the on-stack hash[] buffer before allocating and copying.

[ 2030.238706] BUG: KASAN: slab-out-of-bounds in ksmbdallocuser+0x278/0x680 [ 2030.240549] Read of size 65535 at addr ffff888121bb6680 by task kworker/4:1/18611 [ 2030.242296] [ 2030.242710] CPU: 4 UID: 0 PID: 18611 Comm: kworker/4:1 Not tainted 7.1.0-next-20260623-virtme #96 PREEMPT(lazy) [ 2030.242732] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 [ 2030.242743] Workqueue: ksmbd-io handleksmbdwork [ 2030.242763] Call Trace: [ 2030.242769] <TASK> [ 2030.242776] dumpstacklvl+0xa2/0xd0 [ 2030.242794] printaddressdescription+0x77/0x200 [ 2030.242815] ? ksmbdallocuser+0x278/0x680 [ 2030.242831] printreport+0x58/0x70 [ 2030.242848] kasanreport+0x117/0x150 [ 2030.242869] ? ksmbdallocuser+0x278/0x680 [ 2030.242888] kasancheckrange+0x3c7/0x3f0 [ 2030.242908] ? ksmbdallocuser+0x278/0x680 [ 2030.242925] asanmemcpy+0x29/0x70 [ 2030.242942] ksmbdallocuser+0x278/0x680 [ 2030.242960] ksmbdloginuser+0xc3/0x120 [ 2030.242978] ntlmauthenticate+0x5e6/0x1b00 [ 2030.243017] ? pfxntlmauthenticate+0x10/0x10 [ 2030.243035] ? ksmbdsessionlookup+0x188/0x1d0 [ 2030.243054] ? pfxksmbdsessionlookup+0x10/0x10 [ 2030.243090] ? sanitizercovtraceswitch+0x7b/0x140 [ 2030.243108] smb2sesssetup+0x1e4a/0x27b0 [ 2030.243126] ? copyfromkernelnofault+0x199/0x300 [ 2030.243156] ? pfxsmb2sesssetup+0x10/0x10 [ 2030.243173] ? getsmb2cmdval+0xe3/0x1c0 [ 2030.243208] handleksmbdwork+0x954/0x1280 [ 2030.243230] ? pfxhandleksmbdwork+0x10/0x10 [ 2030.243249] ? processscheduledworks+0xa07/0x1490 [ 2030.243270] ? processscheduledworks+0xa07/0x1490 [ 2030.243291] processscheduledworks+0xa70/0x1490 [ 2030.243320] ? pfxprocessscheduledworks+0x10/0x10 [ 2030.243340] ? dorawspinlock+0x130/0x300 [ 2030.243358] ? lockisheldtype+0x7b/0x110 [ 2030.243388] workerthread+0x932/0xe20 [ 2030.243415] kthread+0x38a/0x470 [ 2030.243431] ? pfxworkerthread+0x10/0x10 [ 2030.243451] ? pfxkthread+0x10/0x10 [ 2030.243467] retfromfork+0x484/0x910 [ 2030.243485] ? pfxretfromfork+0x10/0x10 [ 2030.243501] ? switchto+0xc77/0x12c0 [ 2030.243523] ? pfxkthread+0x10/0x10 [ 2030.243540] retfromforkasm+0x1a/0x30 [ 2030.243564] </TASK> [ 2030.243570] [ 2030.290164] Allocated by task 19279: [ 2030.290911] kasansavetrack+0x3e/0x80 [ 2030.292179] kasankmalloc+0x72/0x90 [ 2030.293217] kvmallocnodenoprof+0x3ff/0x6b0 [ 2030.294467] handlegenericevent+0x59b/0x750 [ 2030.295345] genlfamilyrcvmsgdoit+0x238/0x340 [ 2030.296553] genlrcvmsg+0x606/0x7b0 [ 2030.297129] netlinkrcvskb+0x22b/0x4a0 [ 2030.298500] genlrcv+0x2d/0x40 [ 2030.299273] netlinkunicast+0x7ba/0x930 [ 2030.300019] netlinksendmsg+0x8c3/0xb00 [ 2030.301073] socksendmsg+0xec/0x140 [ 2030.301579] syssendto+0x357/0x470 [ 2030.302255] x64syssendto+0xe3/0x100 [ 2030.303425] dosyscall64+0x135/0x460 [ 2030.304763] entrySYSCALL64afterhwframe+0x77/0x7f [ 2030.305594] [ 2030.305819] The buggy address belongs to the object at ffff888121bb6640 [ 2030.305819] which belongs to the cache kmalloc-192 of size 192 [ 2030.309595] The buggy address ---truncated---(CVE-2026-90174)

In the Linux kernel, the following vulnerability has been resolved:

ocfs2: validate orphan slot during inode read

Patch series "ocfs2: validate active orphan slots during inode read".

OCFS2 trusts active ordinary and append-DIO orphan slots read from dinodes. A corrupted slot can therefore index osborphanwipes or the slot-local system-inode cache outside their allocations before the corruption is reported.

Patch 1 validates the ordinary orphan slot used by inode wipe processing. Patch 2 validates the append-DIO orphan slot used by DIO completion and orphan recovery. Both checks reject corrupt metadata at the existing inode validation boundary.

This patch (of 2):

[BUG] A corrupted dinode with OCFS2ORPHANEDFL can carry an iorphanedslot outside the mounted filesystem slot range. ocfs2wipeinode() uses it to index osborphanwipes before looking up the orphan directory, causing an out-of-bounds memory access.

BUG: KASAN: slab-use-after-free in ocfs2getsystemfileinode+0x780/0x820 fs/ocfs2/sysfile.c:102 Read of size 8 at addr ffff88800b767c00 by task kworker/u8:3/85 Call Trace: ... ocfs2getsystemfileinode+0x780/0x820 fs/ocfs2/sysfile.c:102 ocfs2wipeinode+0x292/0xf70 fs/ocfs2/inode.c:840 ocfs2deleteinode fs/ocfs2/inode.c:1155 [inline] ocfs2evictinode+0x6c9/0x1170 fs/ocfs2/inode.c:1295 evict+0x38e/0x8f0 fs/inode.c:810 iputfinal fs/inode.c:1914 [inline] iput fs/inode.c:1966 [inline] iput+0x55b/0x8b0 fs/inode.c:1926 ocfs2recoverorphans+0x610/0xe40 fs/ocfs2/journal.c:2374 ocfs2completerecovery+0x5af/0xd00 fs/ocfs2/journal.c:1373 ...

[CAUSE] ocfs2validateinodeblock() validates isuballocslot but leaves the active ordinary orphan slot unchecked. Downstream consumers assume that the value is smaller than osb->maxslots.

[FIX] Reject an active iorphanedslot outside the slot range during dinode validation, before the inode reaches orphan wipe processing.(CVE-2026-90205)

In the Linux kernel, the following vulnerability has been resolved:

firmware: coreboot: Validate table bounds

The existing coreboottablepopulate() bounds checks limit individual entries to the mapped length. However, coreboottableprobe() replaces the platform resource length with header and table sizes supplied by firmware before mapping the full table.

A malformed table can overflow the 32-bit size addition or advertise an extent beyond the resource, causing the driver to map and parse memory outside the resource. A resource shorter than the fixed header is also mapped as though it contained a complete header.

Reject resources shorter than the fixed header. After validating the signature, require a complete header, calculate the advertised extent with overflow checking, and reject extents beyond the resource before remapping the table.(CVE-2026-90341)

In the Linux kernel, the following vulnerability has been resolved:

power: supply: sc2731charger: cancel work on remove

The USB notifier and initial charger detection can schedule info->work. The remove path unregisters the notifier, but does not cancel queued or running work before the devm-allocated driver data is released.

Set the platform drvdata used by remove, then cancel the work after unregistering the notifier.

This issue was found by a static analysis tool.(CVE-2026-90394)

In the Linux kernel, the following vulnerability has been resolved:

vhost-scsi: flush backend after device ioctls

vhost-scsi translates guest response descriptors into userspace iovecs when commands are submitted. Target-core completes those commands asynchronously, so VHOSTSETMEMTABLE can replace the memory table while an in-flight command still retains response iovecs translated through the old table.

If the old mapping is reused after VHOSTSETMEMTABLE returns, command completion can write the response to an unrelated userspace object.

Flush the vhost-scsi backend after vhostdevioctl() handles a device ioctl. This waits for in-flight commands that can still use the old response iovecs before the ioctl returns.(CVE-2026-93782)

In the Linux kernel, the following vulnerability has been resolved:

smb: client: reject userspace cifs.idmap descriptions

cifs.idmap key descriptions carry authority-bearing fields (owner and group SIDs and uid/gid values in "os:"/"gs:"/"oi:"/"gi:" form) that the cifs.idmap upcall helper treats as kernel-originating inputs. Unlike its sibling cifs.spnego, the cifs.idmap key type has no vetdescription hook, so userspace can create keys of this type through requestkey(2)/addkey(2) and supply those fields without CIFS origin. A requestkey(2) call with a non-NULL callout then drives a root usermodehelper upcall (/sbin/request-key -> cifs.idmap) that consumes the unvetted description in root context.

Only accept cifs.idmap descriptions while CIFS is using its private rootcred to request the key. idtosid()/sidtoid() already run under overridecreds(rootcred), so the kernel-originated path is unaffected.

This mirrors commit 3da1fdf4efbc ("smb: client: reject userspace cifs.spnego descriptions"), which applied the same restriction to cifs.spnego.(CVE-2026-97564)

In the Linux kernel, the following vulnerability has been resolved:

iio: accel: kxcjk-1013: reject duplicate event disable

The IIO core does not filter duplicate writes to the event enable attribute. kxcjk1013writeeventconfig() already ignores repeated enable requests, but a repeated disable request still calls kxcjk1013setpowerstate(data, false), dropping a runtime PM reference that was not acquired for this request. This can underflow the runtime PM usage count and trigger a "Runtime PM usage count underflow" warning.

Return early when the requested state already matches evenablestate.(CVE-2026-98679)

In the Linux kernel, the following vulnerability has been resolved:

wifi: mac80211: set info->band for 802.3 encap offload frames

Unlike the 802.11 TX paths, ieee802118023xmit() does not set info->band from the channel context on non-MLD interfaces. It stays at 0, so ieee80211gettxrates() uses the wrong band for these frames.

Set it the same way as ieee80211buildhdr(): drop the frame if there is no channel context, and leave the band at 0 on MLD interfaces.(CVE-2026-98700)

In the Linux kernel, the following vulnerability has been resolved:

mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ

The Cadence NAND interrupt handler uses both the IRQ lock and completion object. Registering the IRQ before initializing them leaves a window in which a pending interrupt can access uninitialized synchronization state.

Initialize them before registering the handler.(CVE-2026-98721)

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: btintel: fix buffer over-read in btintelhwerror()

The "Exception info %s" print uses skb->data + 1, but the 12-byte payload is not guaranteed to be NUL-terminated and can be read past its end.

Bound the print with "%.s" and skb->len - 1.(CVE-2026-98732)

In the Linux kernel, the following vulnerability has been resolved:

net: cpswnew: unregister devlink on port registration failure

cpswprobe() registers devlink before registering the CPSW ports.

If cpswregisterports() fails, the error path only unregisters the notifiers and then releases the lower level resources. It does not undo the successful cpswregisterdevlink() call, leaving the devlink instance and its parameters registered after probe has failed.

Add a devlink cleanup label for the path where devlink registration has already succeeded, and use it when port registration fails.(CVE-2026-98909)

In the Linux kernel, the following vulnerability has been resolved:

keys: Protect the type name while describing a key

keyctldescribekey() must keep the key type's name alive until kasprintf() has consumed it. The retained key reference keeps the key and its description alive, but does not pin the module providing its type. The name is passed to kasprintf() without holding key->sem.

kvasprintf() uses the saved name pointer in two formatting passes, with a GFPKERNEL allocation between them. With AFRXRPC=m, a task that passes View permission before type retirement can overlap a privileged module unload in this order:

1. KEYCTLDESCRIBE looks up the key, saves key->type->name in the kasprintf() arguments and completes the first formatting pass. 2. While the formatter is delayed before its second pass, afrxrpcexit() calls unregisterkeytype(), which removes the type from the registry and waits for keygckeytype(). 3. The collector takes key->sem for writing, retypes the retained key to keytypedead and completes retirement. Unregistration and module exit return, allowing freemodule() to release the type and name. 4. The formatter resumes its second pass and reads the saved name from released module storage, which can fault in string().

Hold key->sem for reading across kasprintf(). The collector then cannot retype the key or complete retirement until both formatting passes have finished. If retirement wins the lock first, formatting uses the core keytypedead name instead. Release the semaphore immediately after kasprintf(), including on allocation failure, before copying to userspace.

Oops report as below:

BUG: unable to handle page fault for address: fffffbfff8054794 #PF: supervisor read access in kernel mode #PF: errorcode(0x0000) - not-present page RIP: 0010:string+0x23f/0x470 Call Trace: vsnprintf+0x330/0x1110(CVE-2026-99224)

Affected Software

1 affected componentFixes available
openeuler/kernel<5.10.0-342.0.0.243.oe2203sp4
5.10.0-342.0.0.243.oe2203sp4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openeuler/kernel to a version that resolves this vulnerability.

    Fixed in 5.10.0-342.0.0.243.oe2203sp4
  2. Compensating control

    In KCOV, move remote-state save/restore temporary storage from the per-CPU area to per-thread storage, while retaining the per-CPU kcov_percpu_data.lock to protect task state.

  3. Compensating control

    In OCFS2 inode validation, reject active ordinary and append-DIO orphan slots outside the mounted filesystem's slot range before orphan processing uses them as indices.

  4. Compensating control

    In dm-verity FEC decoding, prevent the erasure-locator loop from writing beyond lambda[]; bound the loop so indices remain within the nroots + 1 element array.

  5. Compensating control

    In the coreboot table driver, reject resources shorter than the fixed header, validate the magic and version, and use overflow-checked extent calculations to reject tables extending beyond the resource.

  6. Compensating control

    In the Prestera firmware parser, reject images shorter than struct prestera_fw_header and reject advertised firmware extents beyond the resource before mapping or parsing them.

  7. Compensating control

    Accept cifs.idmap key descriptions only while CIFS is using its private usermodehelper upcall.

  8. Compensating control

    In key description formatting, hold key->sem for reading across kasprintf() and release it only after formatting has consumed the key type name.

  9. Compensating control

    In ksmbd_alloc_user(), reject responses whose hash_sz exceeds KSMBD_REQ_MAX_HASH_SZ before allocating or copying the passkey.

  10. Compensating control

    In wcove_read_rx_buffer(), clamp the receive loop to sizeof(struct pd_message) and read each register into an unsigned int before storing it in the byte destination.

  11. Compensating control

    For X.25 socket timers, hold a socket reference while a timer is armed, release it on expiry and cancellation, arm with sk_reset_timer(), cancel with sk_stop_timer(), and rearm the heartbeat only while sk_hashed(sk) is true.

  12. Compensating control

    In cpsw_new, unregister devlink on the error path when CPSW port registration fails.

  13. Compensating control

    In vhost-scsi, flush the backend after vhost_dev_ioctl() handles a device ioctl and before the ioctl returns.

  14. Compensating control

    In the SC2731 charger remove path, unregister the notifier and cancel queued or running info->work before releasing driver data.

  15. Compensating control

    In kxcjk1013_write_event_config(), return early when the requested state already matches ev_enable_state.

  16. Compensating control

    Initialize the Cadence NAND IRQ lock and completion before requesting the IRQ.

  17. Compensating control

    Initialize snd_harmony_create()'s locks, including h->mixer_lock, before requesting the IRQ.

  18. Compensating control

    In ieee80211_8023_xmit(), set info->band from the channel context on non-MLD interfaces; drop the frame when there is no channel context, and leave the band at 0 on MLD interfaces.

  19. Compensating control

    Bound the Bluetooth btintel hardware-error string print with "%.*s" using skb->len - 1 as the precision.

Event History

Nov 19, 2026
Advisory Published
via OSV·01:42 AM
Data Sourced
via OSV·01:42 AM
DescriptionSeverityAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203