{"id":"OESA-2026-4898","summary":"kernel security update","details":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: wcove: don&apos;t write past struct pd_message in wcove_read_rx_buffer()\n\nwcove_read_rx_buffer() copies the PD RX FIFO into the caller&apos;s\nstruct pd_message with\n\n\tfor (i = 0; i &lt; USBC_RXINFO_RXBYTES(info); i++)\n\t\tregmap_read(wcove-&gt;regmap, USBC_RX_DATA + i, msg + i);\n\nwhich has two problems:\n\nUSBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_message\nis 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).\nThe byte count latched in RXINFO is the number of bytes the port partner\nput on the wire, so a malicious partner that transmits a 31-byte frame\ncan drive the loop one byte past the destination if the WCOVE BMC\nreceiver does not enforce the PD object-count limit in hardware. The\nexisting FIXME flagged this as unverified.\n\nIndependently, regmap_read() takes an unsigned int * and stores a full\nunsigned int at the destination. Passing the byte pointer msg + i means\neach iteration writes four bytes; the high three are zero (val_bits is\n8) and are normally overwritten by the next iteration, but the final\niteration&apos;s high bytes are not. With RXBYTES == 30 the i == 29 iteration\nalready writes three zero bytes past msg, which sits on the IRQ thread&apos;s\nstack in wcove_typec_irq().\n\nClamp the loop to sizeof(struct pd_message) and read each register into\na local before storing only its low byte, so the copy can never exceed\nthe destination regardless of what RXINFO reports.(CVE-2026-63960)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndm-verity: fix buffer overflow in FEC calculation\n\nThere&apos;s a buffer overflow in dm-verity-fec:\n\nif (neras &amp;&amp; *neras &lt;= v-&gt;fec-&gt;roots)\n\tfio-&gt;erasures[(*neras)++] = i;\n\nThis allows *neras to reach roots + 1 (the post-increment pushes it past\nroots). This value is then passed as no_eras to decode_rs8(). Inside the\nRS decoder (lib/reed_solomon/decode_rs.c:113-121), the erasure locator\npolynomial loop writes lambda[j] where j can reach nroots + 1 — one\nelement past the end of lambda[] (which is sized nroots + 1, valid\nindices 0..nroots). The out-of-bounds write lands on syn[0], corrupting\nthe syndrome buffer.(CVE-2026-72098)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/x25: fix use-after-free of the socket by its timers\n\nThe x25 timers are armed with mod_timer() and cancelled with\ntimer_delete(), so a pending timer holds no reference on the socket and a\ncancel does not wait for a callback already running on another CPU.\n\nx25_heartbeat_expiry() also rearms unconditionally, so it can reinstall\nsk-&gt;sk_timer after __x25_destroy_socket() has passed its cancel point.\nThe following __sock_put() frees the socket while the timer is still\nqueued, and the next expiry uses freed memory.  KASAN reports a\nslab-use-after-free on the kmalloc-2k object freed by close().\n\ntimer_delete_sync() cannot be used here: x25_heartbeat_expiry() and\nx25_timer_expiry() both reach the cancels from inside the timer they\nwould wait on, through __x25_destroy_socket() and x25_disconnect().\n\nArm the timers with sk_reset_timer() and cancel them with sk_stop_timer()\nso that an armed timer owns a reference, and release it in both expiry\nhandlers.  Rearm the heartbeat only while sk_hashed(sk) is still true,\nsince __x25_destroy_socket() unlinks the socket before dropping it.  Arm\nthe deferred destroy timer the same way and drop its reference in\nx25_destroy_timer().\n\nReproduced on net with KASAN, with the heartbeat period shortened so the\nwindow recurs.  With this patch the reproducer no longer triggers a\nreport and /proc/net/x25 drains.\n\nDiscovered by XBOW, triaged by Baul Lee &lt;baul.lee@xbow.com&gt;(CVE-2026-74628)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: prestera: validate firmware header length\n\nprestera_fw_hdr_parse() reads the firmware header before checking\nthat the firmware image contains that header.\n\nReject images shorter than struct prestera_fw_header before decoding the\nmagic and version fields.(CVE-2026-74693)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nkcov: fix data corruption and race conditions on PREEMPT_RT\n\nsyzbot is reporting KCOV state corruption on PREEMPT_RT kernels, for the\ntemporary storage used for saving/restoring remote KCOV state is currently\nallocated as the per-CPU area.\n\nOn PREEMPT_RT kernels, softirq handlers run as preemptible task threads\n(e.g., ksoftirqd). If a softirq context preempts a task running a remote\nKCOV session, it safely saves the task&apos;s state into the per-CPU area.\nHowever, if that softirq thread is subsequently preempted by a higher-\npriority softirq thread on the same CPU, the second softirq will overwrite\nthe same per-CPU area, permanently destroying the original task&apos;s KCOV\nstate.\n\nFix this data corruption by moving the temporary storage from the per-CPU\narea to the per-thread area. Since each softirq thread now owns its own\ntask context, nested softirq preemption no longer causes data overwrites.\n\nNote that while the temporary storage is now on a per-thread basis, the\nper-CPU kcov_percpu_data.lock must be retained, for we need to ensure that\nkcov_remote_start() and kcov_remote_stop() operate atomically without\nracing against asynchronous interrupts that manipulate the current task&apos;s\nKCOV state.\n\nIt is likely that GFP_KERNEL allocation by vmalloc_node() in kcov_init()\nhas already called panic() before returning NULL, for there will be no\nOOM-killable userspace processes when __init function of built-in module\nruns. But this patch also fixes crashing the kernel when vmalloc_node()\nin kcov_init() returned NULL, for kcov_init() left per-CPU irq_area == NULL\nbut kcov_remote_start() depends on per-CPU irq_area != NULL, resulting in\n\n  (1) doing vmalloc() in kcov_remote_start() despite !in_task() context\n\n  (2) out-of-array-bounds access if (1) succeeded but\n      kcov-&gt;remote_size &lt; CONFIG_KCOV_IRQ_AREA_SIZE\n\n  (3) always leak memory allocated by (1), eventually killing all\n      OOM-killable userspace processes\n\nproblems.(CVE-2026-80916)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: harmony: initialize locks before requesting IRQ\n\nsnd_harmony_create() registers the IRQ before initializing h-&gt;lock and\nh-&gt;mixer_lock. A pending interrupt can invoke the handler while these\nlocks are uninitialized.\n\nInitialize both locks before requesting the IRQ so the handler always\nsees valid lock state.(CVE-2026-89980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output()\n\nThe snd_usbmidi_us122l_output() picks a count of 2 on anything slower\nthan high speed and never relates it to ep-&gt;max_transfer.  The URB\nbuffer holds exactly max_transfer bytes, so a device declaring a one\nbyte bulk endpoint takes two bytes from snd_rawmidi_transmit(), and the\nmemset that pads the rest computes 1 - 2 in int and wraps to SIZE_MAX.\n\nOnly 0x800e and 0x800f are pinned to nine bytes.  The US-122MKII at\n0x0644:0x8021 falls to the default and takes usb_maxpacket(), which the\nUSB core only clamps downward.\n\nThe akai and novation output ops in this file were given the same guard\nrecently.  Do the same here.(CVE-2026-90033)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix slab-out-of-bounds read in ksmbd_alloc_user()\n\nksmbd_alloc_user() copies resp-&gt;hash_sz bytes out of the mountd IPC\nlogin response with\n\n\tuser-&gt;passkey_sz = resp-&gt;hash_sz;\n\tuser-&gt;passkey = kmalloc(resp-&gt;hash_sz, KSMBD_DEFAULT_GFP);\n\tif (user-&gt;passkey)\n\t\tmemcpy(user-&gt;passkey, resp-&gt;hash, resp-&gt;hash_sz);\n\nresp-&gt;hash_sz is a __u16 supplied by the response, but resp-&gt;hash[] is\nonly KSMBD_REQ_MAX_HASH_SZ bytes.  A malformed or malicious login\nresponse can set hash_sz well beyond that (up to 65535), so the memcpy()\nreads past the end of the response object.  ipc_validate_msg() does not\nbound hash_sz, so reject any response whose hash_sz exceeds the on-stack\nhash[] buffer before allocating and copying.\n\n[ 2030.238706] BUG: KASAN: slab-out-of-bounds in ksmbd_alloc_user+0x278/0x680\n[ 2030.240549] Read of size 65535 at addr ffff888121bb6680 by task kworker/4:1/18611\n[ 2030.242296]\n[ 2030.242710] CPU: 4 UID: 0 PID: 18611 Comm: kworker/4:1 Not tainted 7.1.0-next-20260623-virtme #96 PREEMPT(lazy)\n[ 2030.242732] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n[ 2030.242743] Workqueue: ksmbd-io handle_ksmbd_work\n[ 2030.242763] Call Trace:\n[ 2030.242769]  &lt;TASK&gt;\n[ 2030.242776]  dump_stack_lvl+0xa2/0xd0\n[ 2030.242794]  print_address_description+0x77/0x200\n[ 2030.242815]  ? ksmbd_alloc_user+0x278/0x680\n[ 2030.242831]  print_report+0x58/0x70\n[ 2030.242848]  kasan_report+0x117/0x150\n[ 2030.242869]  ? ksmbd_alloc_user+0x278/0x680\n[ 2030.242888]  kasan_check_range+0x3c7/0x3f0\n[ 2030.242908]  ? ksmbd_alloc_user+0x278/0x680\n[ 2030.242925]  __asan_memcpy+0x29/0x70\n[ 2030.242942]  ksmbd_alloc_user+0x278/0x680\n[ 2030.242960]  ksmbd_login_user+0xc3/0x120\n[ 2030.242978]  ntlm_authenticate+0x5e6/0x1b00\n[ 2030.243017]  ? __pfx_ntlm_authenticate+0x10/0x10\n[ 2030.243035]  ? ksmbd_session_lookup+0x188/0x1d0\n[ 2030.243054]  ? __pfx_ksmbd_session_lookup+0x10/0x10\n[ 2030.243090]  ? __sanitizer_cov_trace_switch+0x7b/0x140\n[ 2030.243108]  smb2_sess_setup+0x1e4a/0x27b0\n[ 2030.243126]  ? copy_from_kernel_nofault+0x199/0x300\n[ 2030.243156]  ? __pfx_smb2_sess_setup+0x10/0x10\n[ 2030.243173]  ? get_smb2_cmd_val+0xe3/0x1c0\n[ 2030.243208]  handle_ksmbd_work+0x954/0x1280\n[ 2030.243230]  ? __pfx_handle_ksmbd_work+0x10/0x10\n[ 2030.243249]  ? process_scheduled_works+0xa07/0x1490\n[ 2030.243270]  ? process_scheduled_works+0xa07/0x1490\n[ 2030.243291]  process_scheduled_works+0xa70/0x1490\n[ 2030.243320]  ? __pfx_process_scheduled_works+0x10/0x10\n[ 2030.243340]  ? do_raw_spin_lock+0x130/0x300\n[ 2030.243358]  ? lock_is_held_type+0x7b/0x110\n[ 2030.243388]  worker_thread+0x932/0xe20\n[ 2030.243415]  kthread+0x38a/0x470\n[ 2030.243431]  ? __pfx_worker_thread+0x10/0x10\n[ 2030.243451]  ? __pfx_kthread+0x10/0x10\n[ 2030.243467]  ret_from_fork+0x484/0x910\n[ 2030.243485]  ? __pfx_ret_from_fork+0x10/0x10\n[ 2030.243501]  ? __switch_to+0xc77/0x12c0\n[ 2030.243523]  ? __pfx_kthread+0x10/0x10\n[ 2030.243540]  ret_from_fork_asm+0x1a/0x30\n[ 2030.243564]  &lt;/TASK&gt;\n[ 2030.243570]\n[ 2030.290164] Allocated by task 19279:\n[ 2030.290911]  kasan_save_track+0x3e/0x80\n[ 2030.292179]  __kasan_kmalloc+0x72/0x90\n[ 2030.293217]  __kvmalloc_node_noprof+0x3ff/0x6b0\n[ 2030.294467]  handle_generic_event+0x59b/0x750\n[ 2030.295345]  genl_family_rcv_msg_doit+0x238/0x340\n[ 2030.296553]  genl_rcv_msg+0x606/0x7b0\n[ 2030.297129]  netlink_rcv_skb+0x22b/0x4a0\n[ 2030.298500]  genl_rcv+0x2d/0x40\n[ 2030.299273]  netlink_unicast+0x7ba/0x930\n[ 2030.300019]  netlink_sendmsg+0x8c3/0xb00\n[ 2030.301073]  __sock_sendmsg+0xec/0x140\n[ 2030.301579]  __sys_sendto+0x357/0x470\n[ 2030.302255]  __x64_sys_sendto+0xe3/0x100\n[ 2030.303425]  do_syscall_64+0x135/0x460\n[ 2030.304763]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[ 2030.305594]\n[ 2030.305819] The buggy address belongs to the object at ffff888121bb6640\n[ 2030.305819]  which belongs to the cache kmalloc-192 of size 192\n[ 2030.309595] The buggy address \n---truncated---(CVE-2026-90174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: validate orphan slot during inode read\n\nPatch series &quot;ocfs2: validate active orphan slots during inode read&quot;.\n\nOCFS2 trusts active ordinary and append-DIO orphan slots read from dinodes.\nA corrupted slot can therefore index osb_orphan_wipes or the slot-local\nsystem-inode cache outside their allocations before the corruption is\nreported.\n\nPatch 1 validates the ordinary orphan slot used by inode wipe processing.\nPatch 2 validates the append-DIO orphan slot used by DIO completion and\norphan recovery.  Both checks reject corrupt metadata at the existing inode\nvalidation boundary.\n\n\nThis patch (of 2):\n\n[BUG]\nA corrupted dinode with OCFS2_ORPHANED_FL can carry an\ni_orphaned_slot outside the mounted filesystem slot range.\nocfs2_wipe_inode() uses it to index osb_orphan_wipes before looking\nup the orphan directory, causing an out-of-bounds memory access.\n\nBUG: KASAN: slab-use-after-free in ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102\nRead of size 8 at addr ffff88800b767c00 by task kworker/u8:3/85\nCall Trace:\n ...\n ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102\n ocfs2_wipe_inode+0x292/0xf70 fs/ocfs2/inode.c:840\n ocfs2_delete_inode fs/ocfs2/inode.c:1155 [inline]\n ocfs2_evict_inode+0x6c9/0x1170 fs/ocfs2/inode.c:1295\n evict+0x38e/0x8f0 fs/inode.c:810\n iput_final fs/inode.c:1914 [inline]\n iput fs/inode.c:1966 [inline]\n iput+0x55b/0x8b0 fs/inode.c:1926\n ocfs2_recover_orphans+0x610/0xe40 fs/ocfs2/journal.c:2374\n ocfs2_complete_recovery+0x5af/0xd00 fs/ocfs2/journal.c:1373\n ...\n\n[CAUSE]\nocfs2_validate_inode_block() validates i_suballoc_slot but leaves\nthe active ordinary orphan slot unchecked. Downstream consumers\nassume that the value is smaller than osb-&gt;max_slots.\n\n[FIX]\nReject an active i_orphaned_slot outside the slot range during\ndinode validation, before the inode reaches orphan wipe processing.(CVE-2026-90205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: coreboot: Validate table bounds\n\nThe existing coreboot_table_populate() bounds checks limit individual\nentries to the mapped length.  However, coreboot_table_probe() replaces\nthe platform resource length with header and table sizes supplied by\nfirmware before mapping the full table.\n\nA malformed table can overflow the 32-bit size addition or advertise an\nextent beyond the resource, causing the driver to map and parse memory\noutside the resource.  A resource shorter than the fixed header is also\nmapped as though it contained a complete header.\n\nReject resources shorter than the fixed header.  After validating the\nsignature, require a complete header, calculate the advertised extent\nwith overflow checking, and reject extents beyond the resource before\nremapping the table.(CVE-2026-90341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: sc2731_charger: cancel work on remove\n\nThe USB notifier and initial charger detection can schedule info-&gt;work.\nThe remove path unregisters the notifier, but does not cancel queued or\nrunning work before the devm-allocated driver data is released.\n\nSet the platform drvdata used by remove, then cancel the work after\nunregistering the notifier.\n\nThis issue was found by a static analysis tool.(CVE-2026-90394)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvhost-scsi: flush backend after device ioctls\n\nvhost-scsi translates guest response descriptors into userspace iovecs\nwhen commands are submitted.  Target-core completes those commands\nasynchronously, so VHOST_SET_MEM_TABLE can replace the memory table while\nan in-flight command still retains response iovecs translated through the\nold table.\n\nIf the old mapping is reused after VHOST_SET_MEM_TABLE returns, command\ncompletion can write the response to an unrelated userspace object.\n\nFlush the vhost-scsi backend after vhost_dev_ioctl() handles a device\nioctl.  This waits for in-flight commands that can still use the old\nresponse iovecs before the ioctl returns.(CVE-2026-93782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: reject userspace cifs.idmap descriptions\n\ncifs.idmap key descriptions carry authority-bearing fields (owner and\ngroup SIDs and uid/gid values in &quot;os:&quot;/&quot;gs:&quot;/&quot;oi:&quot;/&quot;gi:&quot; form) that the\ncifs.idmap upcall helper treats as kernel-originating inputs.  Unlike\nits sibling cifs.spnego, the cifs.idmap key type has no vet_description\nhook, so userspace can create keys of this type through\nrequest_key(2)/add_key(2) and supply those fields without CIFS origin.\nA request_key(2) call with a non-NULL callout then drives a root\nusermodehelper upcall (/sbin/request-key -&gt; cifs.idmap) that consumes\nthe unvetted description in root context.\n\nOnly accept cifs.idmap descriptions while CIFS is using its private\nroot_cred to request the key.  id_to_sid()/sid_to_id() already run\nunder override_creds(root_cred), so the kernel-originated path is\nunaffected.\n\nThis mirrors commit 3da1fdf4efbc (&quot;smb: client: reject userspace\ncifs.spnego descriptions&quot;), which applied the same restriction to\ncifs.spnego.(CVE-2026-97564)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: accel: kxcjk-1013: reject duplicate event disable\n\nThe IIO core does not filter duplicate writes to the event enable\nattribute. kxcjk1013_write_event_config() already ignores repeated\nenable requests, but a repeated disable request still calls\nkxcjk1013_set_power_state(data, false), dropping a runtime PM reference\nthat was not acquired for this request. This can underflow the runtime\nPM usage count and trigger a &quot;Runtime PM usage count underflow&quot; warning.\n\nReturn early when the requested state already matches ev_enable_state.(CVE-2026-98679)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: set info-&gt;band for 802.3 encap offload frames\n\nUnlike the 802.11 TX paths, ieee80211_8023_xmit() does not set\ninfo-&gt;band from the channel context on non-MLD interfaces. It stays at\n0, so ieee80211_get_tx_rates() uses the wrong band for these frames.\n\nSet it the same way as ieee80211_build_hdr(): drop the frame if there is\nno channel context, and leave the band at 0 on MLD interfaces.(CVE-2026-98700)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtd: rawnand: cadence: Initialize IRQ state before requesting IRQ\n\nThe Cadence NAND interrupt handler uses both the IRQ lock and completion\nobject. Registering the IRQ before initializing them leaves a window in\nwhich a pending interrupt can access uninitialized synchronization state.\n\nInitialize them before registering the handler.(CVE-2026-98721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btintel: fix buffer over-read in btintel_hw_error()\n\nThe &quot;Exception info %s&quot; print uses skb-&gt;data + 1, but the 12-byte\npayload is not guaranteed to be NUL-terminated and can be read past\nits end.\n\nBound the print with &quot;%.*s&quot; and skb-&gt;len - 1.(CVE-2026-98732)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: cpsw_new: unregister devlink on port registration failure\n\ncpsw_probe() registers devlink before registering the CPSW ports.\n\nIf cpsw_register_ports() fails, the error path only unregisters the\nnotifiers and then releases the lower level resources. It does not undo\nthe successful cpsw_register_devlink() call, leaving the devlink instance\nand its parameters registered after probe has failed.\n\nAdd a devlink cleanup label for the path where devlink registration has\nalready succeeded, and use it when port registration fails.(CVE-2026-98909)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nkeys: Protect the type name while describing a key\n\nkeyctl_describe_key() must keep the key type&apos;s name alive until\nkasprintf() has consumed it. The retained key reference keeps the key\nand its description alive, but does not pin the module providing its\ntype. The name is passed to kasprintf() without holding key-&gt;sem.\n\nkvasprintf() uses the saved name pointer in two formatting passes, with\na GFP_KERNEL allocation between them. With AF_RXRPC=m, a task that\npasses View permission before type retirement can overlap a privileged\nmodule unload in this order:\n\n1. KEYCTL_DESCRIBE looks up the key, saves key-&gt;type-&gt;name in the\n   kasprintf() arguments and completes the first formatting pass.\n2. While the formatter is delayed before its second pass,\n   af_rxrpc_exit() calls unregister_key_type(), which removes the type\n   from the registry and waits for key_gc_keytype().\n3. The collector takes key-&gt;sem for writing, retypes the retained key\n   to key_type_dead and completes retirement. Unregistration and module\n   exit return, allowing free_module() to release the type and name.\n4. The formatter resumes its second pass and reads the saved name from\n   released module storage, which can fault in string().\n\nHold key-&gt;sem for reading across kasprintf(). The collector then cannot\nretype the key or complete retirement until both formatting passes have\nfinished. If retirement wins the lock first, formatting uses the core\nkey_type_dead name instead. Release the semaphore immediately after\nkasprintf(), including on allocation failure, before copying to\nuserspace.\n\nOops report as below:\n\n    BUG: unable to handle page fault for address: fffffbfff8054794\n    #PF: supervisor read access in kernel mode\n    #PF: error_code(0x0000) - not-present page\n    RIP: 0010:string+0x23f/0x470\n    Call Trace:\n     vsnprintf+0x330/0x1110(CVE-2026-99224)","modified":"2026-11-19T02:01:11.651595717Z","published":"2026-11-19T01:42:50Z","upstream":["CVE-2026-63960","CVE-2026-72098","CVE-2026-74628","CVE-2026-74693","CVE-2026-80916","CVE-2026-89980","CVE-2026-90033","CVE-2026-90174","CVE-2026-90205","CVE-2026-90341","CVE-2026-90394","CVE-2026-93782","CVE-2026-97564","CVE-2026-98679","CVE-2026-98700","CVE-2026-98721","CVE-2026-98732","CVE-2026-98909","CVE-2026-99224"],"database_specific":{"severity":"Critical"},"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4898"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63960"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72098"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74628"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74693"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80916"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89980"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90033"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90174"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90205"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90341"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90394"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93782"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97564"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98679"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98700"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98721"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98732"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98909"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99224"}],"affected":[{"package":{"name":"kernel","ecosystem":"openEuler:22.03-LTS-SP4","purl":"pkg:rpm/openEuler/kernel&distro=openEuler-22.03-LTS-SP4"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-342.0.0.243.oe2203sp4"}]}],"ecosystem_specific":{"aarch64":["bpftool-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","bpftool-debuginfo-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-debuginfo-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-debugsource-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-devel-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-headers-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-source-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-tools-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-tools-debuginfo-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","kernel-tools-devel-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","perf-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","perf-debuginfo-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","python3-perf-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm","python3-perf-debuginfo-5.10.0-342.0.0.243.oe2203sp4.aarch64.rpm"],"src":["kernel-5.10.0-342.0.0.243.oe2203sp4.src.rpm"],"x86_64":["bpftool-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","bpftool-debuginfo-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-debuginfo-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-debugsource-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-devel-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-headers-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-source-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-tools-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-tools-debuginfo-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","kernel-tools-devel-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","perf-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","perf-debuginfo-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","python3-perf-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm","python3-perf-debuginfo-5.10.0-342.0.0.243.oe2203sp4.x86_64.rpm"]},"database_specific":{"source":"https://repo.openeuler.org/security/data/osv/OESA-2026-4898.json"}}],"schema_version":"1.9.2","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}]}