CVE-2023-54259

Root has patched CVE-2023-54259 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.

• crypto: algif_aead - Fix minimum RX size check for decryption {CVE-2026-31431}
• crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl {CVE-2026-31431}
• crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec {CVE-2026-31431}
• crypto: authencesn - Fix src offset when decrypting in-place {CVE-2026-31431}
• crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption {CVE-2026-31431}
• crypto: authenc - use memcpy_sglist() instead of null skcipher {CVE-2026-31431}
• crypto: algif_aead - snapshot IV for async AEAD requests {CVE-2026-31431}
• crypto: algif_aead - Revert to operating out-of-place {CVE-2026-31431}
• crypto: algif_aead - use memcpy_sglist() instead of null skcipher {CVE-2026-31431}
• crypto: scatterwalk - Backport memcpy_sglist() {CVE-2026-31431}
• wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() {CVE-2022-50551}
• bonding: limit BOND_MODE_8023AD to Ethernet devices {CVE-2026-23099}
• libceph: make decode_pool() more resilient against corrupted osdmaps {CVE-2025-71116}
• scsi: qla2xxx: Fix bsg_done() causing double free {CVE-2025-71238}
• ftrace: Fix use-after-free for dynamic ftrace_ops {CVE-2022-49892}
• intel_th: msu: Fix vmalloced buffers {CVE-2022-50142}
• vt: Clear selection before changing the font {CVE-2022-49948}
• ACPICA: Fix error code path in acpi_ds_call_control_method() {CVE-2022-50411}
• usbnet: Run unregister_netdev() before unbind_all() {CVE-2022-50220}
• ipvs: fix WARNING in ip_vs_app_net_cleanup() {CVE-2022-49917}
• bpf: Propagate error from htab_lock_bucket() to userspace {CVE-2022-50490}
• binfmt_misc: fix shift-out-of-bounds in check_special_flags {CVE-2022-50497}
• module: fix [e_shstrndx].sh_size=0 OOB access {CVE-2022-49444}
• ceph: avoid putting the realm twice when decoding snaps fails {CVE-2022-49770}
• tracing: Fix potential double free in create_var_ref() {CVE-2022-49410}
• powercap: intel_rapl: fix UBSAN shift-out-of-bounds issue {CVE-2022-50366}
• Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times {CVE-2022-50419}
• xsk: Fix xsk_diag use-after-free error during socket cleanup {CVE-2023-53426}
• svcrdma: bound check rq_pages index in inline path {CVE-2025-71068}
• net: hns3: add VLAN id validation before using {CVE-2025-71112}
• net: mdio: fix undefined behavior in bit shift for __mdiobus_register {CVE-2022-49907}
• capabilities: fix undefined behavior in bit shift for CAP_TO_MASK {CVE-2022-49870}
• ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS {CVE-2022-50315}
• i2c: piix4: Fix adapter not be removed in piix4_remove() {CVE-2022-49900}
• team: fix check for port enabled in team_queue_override_port_prio_changed() {CVE-2025-71091}
• staging: vme_user: Fix possible UAF in tsi148_dma_list_add {CVE-2022-50384}
• ALSA: ctxfi: Fix potential OOB access in audio mixer handling {CVE-2026-23076}
• ftrace: Add cond_resched() to ftrace_graph_set_hash() {CVE-2025-37940}
• net: stmmac: Fix accessing freed irq affinity_hint {CVE-2025-23155}
• ext4: set goal start correctly in ext4_mb_normalize_request {CVE-2023-54021}
• netfilter: ipset: fix region locking in hash types {CVE-2025-37997}
• openvswitch: Fix unsafe attribute parsing in output_userspace() {CVE-2025-37998}
• wifi: brcm80211: fmac: Add error handling for brcmf_usb_dl_writeimage() {CVE-2025-37990}
• nfs: handle failure of nfs_get_lock_context in unlock path {CVE-2025-38023}
• drm/amd/pm: Prevent division by zero {CVE-2025-37767}
• netfilter: ctnetlink: remove refcounting in expectation dumpers {CVE-2025-39764}
• tracing: Fix null pointer dereference in tracing_err_log_open() {CVE-2023-53167}
• ACPICA: Refuse to evaluate a method if arguments are missing {CVE-2025-38386}
• scsi: qla2xxx: Pointer may be dereferenced {CVE-2023-53150}
• net: pktgen: fix access outside of user given buffer in pktgen_thread_write() {CVE-2025-38061}
• dm cache: prevent BUG_ON by blocking retries on failed device resumes {CVE-2025-38066} -…

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

soundwire: bus: Fix unbalanced pm_runtime_put() causing usage count underflow

This reverts commit 443a98e649b4 ("soundwire: bus: use pm_runtime_resume_and_get()")

Change calls to pm_runtime_resume_and_get() back to pm_runtime_get_sync(). This fixes a usage count underrun caused by doing a pm_runtime_put() even though pm_runtime_resume_and_get() returned an error.

The three affected functions ignore -EACCES error from trying to get pm_runtime, and carry on, including a put at the end of the function. But pm_runtime_resume_and_get() does not increment the usage count if it returns an error. So in the -EACCES case you must not call pm_runtime_put().

The documentation for pm_runtime_get_sync() says: "Consider using pm_runtime_resume_and_get() ... as this is likely to result in cleaner code."

In this case I don't think it results in cleaner code because the pm_runtime_put() at the end of the function would have to be conditional on the return value from pm_runtime_resume_and_get() at the top of the function.

pm_runtime_get_sync() doesn't have this problem because it always increments the count, so always needs a put. The code can just flow through and do the pm_runtime_put() unconditionally.

In the Linux kernel, the following vulnerability has been resolved: soundwire: bus: Fix unbalanced pm_runtime_put() causing usage count underflow This reverts commit 443a98e649b4 ("soundwire: bus: use pm_runtime_resume_and_get()") Change calls to pm_runtime_resume_and_get() back to pm_runtime_get_sync(). This fixes a usage count underrun caused by doing a pm_runtime_put() even though pm_runtime_resume_and_get() returned an error. The three affected functions ignore -EACCES error from trying to get pm_runtime, and carry on, including a put at the end of the function. But pm_runtime_resume_and_get() does not increment the usage count if it returns an error. So in the -EACCES case you must not call pm_runtime_put(). The documentation for pm_runtime_get_sync() says: "Consider using pm_runtime_resume_and_get() ... as this is likely to result in cleaner code." In this case I don't think it results in cleaner code because the pm_runtime_put() at the end of the function would have to be conditional on the return value from pm_runtime_resume_and_get() at the top of the function. pm_runtime_get_sync() doesn't have this problem because it always increments the count, so always needs a put. The code can just flow through and do the pm_runtime_put() unconditionally.

In the Linux kernel, the following vulnerability has been resolved: soundwire: bus: Fix unbalanced pm_runtime_put() causing usage count underflow This reverts commit 443a98e649b4 ("soundwire: bus: use pm_runtime_resume_and_get()") Change calls to pm_runtime_resume_and_get() back to pm_runtime_get_sync(). This fixes a usage count underrun caused by doing a pm_runtime_put() even though pm_runtime_resume_and_get() returned an error. The three affected functions ignore -EACCES error from trying to get pm_runtime, and carry on, including a put at the end of the function. But pm_runtime_resume_and_get() does not increment the usage count if it returns an error. So in the -EACCES case you must not call pm_runtime_put(). The documentation for pm_runtime_get_sync() says: "Consider using pm_runtime_resume_and_get() ... as this is likely to result in cleaner code." In this case I don't think it results in cleaner code because the pm_runtime_put() at the end of the function would have to be conditional on the return value from pm_runtime_resume_and_get() at the top of the function. pm_runtime_get_sync() doesn't have this problem because it always increments the count, so always needs a put. The code can just flow through and do the pm_runtime_put() unconditionally.