CLSA-2026-1795166263: kernel: Fix of 33 CVEs

Published Nov 20, 2026
·
Updated

- net/sched: schteql: Introduce slaveslock to avoid race condition and UAF {CVE-2026-72390} - lockd: handle lockowner allocation failure in nlmclntproc() {CVE-2026-89484} - ubi: ubiwlputpeb: Fix infinite loop when wear-leveling work failed - UBI: fix use-after-free on error path {CVE-2023-53826} - proc: protect ptracemayaccess() with execupdatelock (FD links) {CVE-2026-64375} - net: pktgen: remove rcu locking in pktgenchangename() {CVE-2026-74479} - net: pktgen: fix proc entry use-after-free {CVE-2026-74479} - lockd: fix NULL dereference on lockowner allocation failure {CVE-2026-89484} - UBI: Fix stale pointers in ubi->lookuptbl {CVE-2023-53826} - xfs: don't dereference a NULL parent in xfsialloc() owner setup {CVE-2021-4037} - tun: Require CAPNETADMIN to attach to an ownerless device {CVE-2026-99281} - xfrm: Duplicate SPI Handling {CVE-2025-39797} - USB: serial: omninet: fix memory corruption with small endpoint {CVE-2026-63928} - wifi: cfg80211: get the wiphy out of a dying network namespace {CVE-2026-98330} - hwrng: virtio: clamp device-reported used.len at copydata() {CVE-2026-64456} - ipvs: avoid out-of-bounds write in ipvsnaticmp {CVE-2026-74724} - sctp: auth: verify auth requirement when authchunk is NULL {CVE-2026-68300} - smb: client: bound dirent name against end of SMB response in cifsfilldir {CVE-2026-93787} - smb: client: reject a tree connect response whose byte count is too small {CVE-2026-89631} - smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() {CVE-2026-97563} - smb: client: reject short READ responses in CIFSSMBRead() {CVE-2026-97565} - keys: Avoid the owner account dereference in named keyring lookup {CVE-2026-99226} - ALSA: mixer: oss: Add card disconnect checkpoints {CVE-2026-43126} - can: bcm: fix hrtimer/tasklet termination in bcm op removal {CVE-2026-17523} - tty: port: fix ttyportttyvhangup() race {CVE-2026-98752} - tty: abort break signalling on hangup {CVE-2026-98751} - usb: core: clear both epin and epout for non-ep0 control endpoints {CVE-2026-98763} - Bluetooth: RFCOMM: fix NULL dereference of dlc->session in RFCOMMCONNINFO {CVE-2026-98455} - ALSA: usb: 6fire: Avoid embedded URBs {CVE-2026-98428} - net: bridge: use DEVSTATSINC() {CVE-2023-52578} - fs: prevent page refcount overflow in pipebufget {CVE-2019-11487} - btrfs: tree-checker: validate names in ROOTREF and ROOTBACKREF {CVE-2026-97415} - scsi: message: mptlan: Fix use after free bug in mptlanremove() due to race condition {CVE-2023-54310} - net: sungem: fix probe error cleanup {CVE-2026-72406} - fbdev: release the console semaphore on the lockfbinfo() failure path - ipvs: fix the checksum validations {CVE-2026-80901} - scsi: libiscsi: Validate the ITT reflected in a Reject PDU {CVE-2026-99153} - ecryptfs: hold msg ctx list lock when cleaning daemon queue {CVE-2026-89609} - ipvs: bound LBLCR and LBLC cache growth {CVE-2026-98857} - ipvs: initialize tbl->entries in ipvslblcinitsvc() {CVE-2026-98857} - ipvs: initialize tbl->entries after allocation {CVE-2026-98857} - USB: serial: keyspan: fix URB unlink {CVE-2026-98772} - perf sched: Fix registerpid() overflow, strcpy, and BUGON {CVE-2026-80671}

Affected Software

10 affected componentsFixes available
tuxcare/kernel<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/kernel-abi-whitelists<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/kernel-debug<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/kernel-debug-devel<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/kernel-devel<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/kernel-doc<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/kernel-firmware<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/kernel-headers<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/perf<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41
tuxcare/python-perf<2.6.32-754.35.8.el6.tuxcare.els41
2.6.32-754.35.8.el6.tuxcare.els41

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  2. Upgrade

    Upgrade tuxcare/kernel-abi-whitelists to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  3. Upgrade

    Upgrade tuxcare/kernel-debug to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  4. Upgrade

    Upgrade tuxcare/kernel-debug-devel to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  5. Upgrade

    Upgrade tuxcare/kernel-devel to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  6. Upgrade

    Upgrade tuxcare/kernel-doc to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  7. Upgrade

    Upgrade tuxcare/kernel-firmware to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  8. Upgrade

    Upgrade tuxcare/kernel-headers to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  9. Upgrade

    Upgrade tuxcare/perf to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41
  10. Upgrade

    Upgrade tuxcare/python-perf to a version that resolves this vulnerability.

    Fixed in 2.6.32-754.35.8.el6.tuxcare.els41

Event History

Nov 20, 2026
Advisory Published
via OSV·09:18 AM
Data Sourced
via OSV·09:18 AM
DescriptionAffected Software

Frequently Asked Questions

1

Which systems are in scope for this advisory?

The advisory applies to systems using the listed TuxCare kernel packages, including tuxcare/kernel and related ABI whitelist, debug, development, documentation, firmware, and header packages.

2

Are the issues limited to one kernel subsystem?

No. The listed fixes span networking, UBI, proc, lockd, XFS, USB serial, Wi-Fi configuration, virtual RNG, and other kernel subsystems. Exposure depends on which affected kernel functionality is enabled and used on a system.

3

What vulnerability classes are addressed?

The advisory identifies use-after-free and race condition weaknesses. The listed fixes also include memory corruption, NULL dereference, out-of-bounds write, stale-pointer, and infinite-loop conditions.

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