Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ OESA-2026-1075 — kernel (CVE-2022-50635 +12 more)

🟠 CVSS 8.0 — High ✅ No Known Exploit OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

kernel security update

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

powerpc/kprobes: Fix null pointer reference in arch_prepare_kprobe()

I found a null pointer reference in arch_prepare_kprobe():

# echo 'p cmdline_proc_show' > kprobe_events

# echo 'p cmdline_proc_show+16' >> kprobe_events

Kernel attempted to read user page (0) - exploit attempt? (uid: 0)

BUG: Kernel NULL pointer dereference on read at 0x00000000

Faulting instruction address: 0xc000000000050bfc

Oops: Kernel access of bad area, sig: 11 [#1]

LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA PowerNV

Modules linked in:

CPU: 0 PID: 122 Comm: sh Not tainted 6.0.0-rc3-00007-gdcf8e5633e2e #10

NIP: c000000000050bfc LR: c000000000050bec CTR: 0000000000005bdc

REGS: c0000000348475b0 TRAP: 0300 Not tainted (6.0.0-rc3-00007-gdcf8e5633e2e)

MSR: 9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 88002444 XER: 20040006

CFAR: c00000000022d100 DAR: 0000000000000000 DSISR: 40000000 IRQMASK: 0

...

NIP arch_prepare_kprobe+0x10c/0x2d0

LR arch_prepare_kprobe+0xfc/0x2d0

Call Trace:

0xc0000000012f77a0 (unreliable)

register_kprobe+0x3c0/0x7a0

__register_trace_kprobe+0x140/0x1a0

__trace_kprobe_create+0x794/0x1040

trace_probe_create+0xc4/0xe0

create_or_delete_trace_kprobe+0x2c/0x80

trace_parse_run_command+0xf0/0x210

probes_write+0x20/0x40

vfs_write+0xfc/0x450

ksys_write+0x84/0x140

system_call_exception+0x17c/0x3a0

system_call_vectored_common+0xe8/0x278

--- interrupt: 3000 at 0x7fffa5682de0

NIP: 00007fffa5682de0 LR: 0000000000000000 CTR: 0000000000000000

REGS: c000000034847e80 TRAP: 3000 Not tainted (6.0.0-rc3-00007-gdcf8e5633e2e)

MSR: 900000000280f033 <SF,HV,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 44002408 XER: 00000000

The address being probed has some special:

cmdline_proc_show: Probe based on ftrace

cmdline_proc_show+16: Probe for the next instruction at the ftrace location

The ftrace-based kprobe does not generate kprobe::ainsn::insn, it gets

set to NULL. In arch_prepare_kprobe() it will check for:

...

prev = get_kprobe(p->addr - 1);

preempt_enable_no_resched();

if (prev && ppc_inst_prefixed(ppc_inst_read(prev->ainsn.insn))) {

...

If prev is based on ftrace, &apos;ppc_inst_read(prev->ainsn.insn)&apos; will occur

with a null pointer reference. At this point prev->addr will not be a

prefixed instruction, so the check can be skipped.

Check if prev is ftrace-based kprobe before reading &apos;prev->ainsn.insn&apos;

to fix this problem.

[mpe: Trim oops](CVE-2022-50635)

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

erofs: validate the extent length for uncompressed pclusters

syzkaller reported a KASAN use-after-free:

https://syzkaller.appspot.com/bug?extid=2ae90e873e97f1faf6f2

The referenced fuzzed image actually has two issues:

  • m_pa == 0 as a non-inlined pcluster;
  • The logical length is longer than its physical length.

The first issue has already been addressed. This patch addresses

the second issue by checking the extent length validity.(CVE-2022-50746)

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

smc: Fix use-after-free in tcp_write_timer_handler().

With Eric&apos;s ref tracker, syzbot finally found a repro for

use-after-free in tcp_write_timer_handler() by kernel TCP

sockets. [0]

If SMC creates a kernel socket in __smc_create(), the kernel

socket is supposed to be freed in smc_clcsock_release() by

calling sock_release() when we close() the parent SMC socket.

However, at the end of smc_clcsock_release(), the kernel

socket&apos;s sk_state might not be TCP_CLOSE. This means that

we have not called inet_csk_destroy_sock() in __tcp_close()

and have not stopped the TCP timers.

The kernel socket&apos;s TCP timers can be fired later, so we

need to hold a refcnt for net as we do for MPTCP subflows

in mptcp_subflow_create_socket().

[0]:

leaked reference.

sk_alloc (./include/net/net_namespace.h:335 net/core/sock.c:2108)

inet_create (net/ipv4/af_inet.c:319 net/ipv4/af_inet.c:244)

__sock_create (net/socket.c:1546)

smc_create (net/smc/af_smc.c:3269 net/smc/af_smc.c:3284)

__sock_create (net/socket.c:1546)

__sys_socket (net/socket.c:1634 net/socket.c:1618 net/socket.c:1661)

__x64_sys_socket (net/socket.c:1672)

do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80)

entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)

==================================================================

BUG: KASAN: slab-use-after-free in tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594)

Read of size 1 at addr ffff888052b65e0d by task syzrepro/18091

CPU: 0 PID: 18091 Comm: syzrepro Tainted: G W 6.3.0-rc4-01174-gb5d54eb5899a #7

Hardware name: QEMU Standard PC (i440FX

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

OESA-2026-1075 is recorded against 1 package.

  • kernel (fixed in 5.10.0-298.0.0.200.oe2203sp3)

Timeline and source

Published on 16 January 2026 and last revised on 18 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

www.openeuler.org (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)
nvd.nist.gov (Advisory)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-01-16
Updated 2026-08-20
Modified 2026-08-18
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel — 5.10.0-298.0.0.200.oe2203sp3

References

Similar Threats

Site Security Check

Is kernel part of your stack?

OESA-2026-1075 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesopenEuleropenEuler 2026
✓