Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Dismissed suggestions

These automatic suggestions were dismissed after initial triaging.

to select a suggestion for revision.

View:
Compact
Detailed
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
ALSA: usb-audio: fix stack info leak in RME Digiface status

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix stack info leak in RME Digiface status snd_rme_digiface_read_status() reads a four-word status block from the device into an uninitialised on-stack __le32 buf[4] and, whenever the vendor control-IN transfer does not return a negative error, copies all four words into the caller's status[]. snd_usb_ctl_msg() copies the full requested size back into the caller's buffer regardless of how many bytes the data stage actually delivered: buf = kmemdup(data, size, GFP_KERNEL); err = usb_control_msg(dev, pipe, request, requesttype, value, index, buf, size, timeout); memcpy(data, buf, size); usb_control_msg() returns the transferred length on a short control-IN, which is a non-negative value, and writes only that many bytes. The remainder of the copy back is the kmemdup()ed image of the caller's buffer, so a device answering with a short data stage leaves the trailing words of buf[] holding leftover kernel stack. The only guard in the caller is err < 0, so those words are stored into status[]. They then reach user space: snd_rme_digiface_get_status_val() selects a 16-bit halfword of status[] per the control's reg/mask, and the eight Digiface status controls together expose the whole 16-byte frame to an unprivileged reader of /dev/snd/controlC*. Zero-initialise the buffer so a short read yields zeros instead of stack residue. This mirrors snd_rme_get_status1(), which already clears its output word before the same kind of vendor read. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>

Affected products

Linux
  • ==6.12
  • <7ba01e0d3539d9cf0aef3e82938f1648147744cc
  • <441aaad150c57edaf57ee482a79a3bf4c5b7e353
  • ==3089703ab71484a8b9a7641051181d11d60f870c
  • =<*
  • <b3a346d5c99dd73cf84711f2a43e42691990efd2
  • <6.12
  • <6.11
  • <6.12
  • =<6.12.*
  • =<6.18.*
  • =<7.1.*
  • ==50f63f11a6ddaa0d34574df72b3fa6ee257c057d
  • <98dbfbb38e297c25c5b0af4a9018d71ac25e8554
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
can: etas_es58x: es58x_read_bulk_callback(): fix RX buffer leak on URB resubmit failure

In the Linux kernel, the following vulnerability has been resolved: can: etas_es58x: es58x_read_bulk_callback(): fix RX buffer leak on URB resubmit failure es58x_read_bulk_callback() resubmits the RX URB after processing a received packet. If the resubmit succeeds, the URB remains anchored and will be handled by the normal RX path or by teardown. However, if usb_submit_urb() fails, the callback unanchors the URB and then returns directly. This skips the existing free_urb path, so the coherent transfer buffer allocated with usb_alloc_coherent() is not released. Reuse the existing free_urb path after a resubmit failure so that the RX coherent buffer is freed before leaving the callback.

Affected products

Linux
  • <b85e5c310382803d27adf6fe6554d4208bc8951c
  • ==7a0171b4921ad443fee5ed4fcb9d99fa4776edac
  • =<6.6.*
  • =<*
  • =<7.1.*
  • ==b8f9ca88253574638bcff38900a4c28d570b1919
  • <6.18.44
  • <6.2
  • <7.0
  • =<6.18.*
  • <0ef136ba052101243ba117a1aca6f4a4c3a81142
  • <6.20
  • <c311f17c261fd375ddf5755f2ebe1f022c19c5b0
  • <5.16
  • ==2185ea6e4ebcb61d1224dc7d187c59723cb5ad59
  • =<6.12.*
  • <7a0cf2b2497c757c3cb1286eddf2986abb0d387b
  • <19c6c8c6cd5dd14fab5fcd744584812a57cbb78d
  • <6.12.103
  • ==7.0
  • <6.6.151
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
RDMA/mlx5: Fix undefined shift of user RQ WQE size

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix undefined shift of user RQ WQE size set_rq_size() computes the RQ WQE size as "1 << rq_wqe_shift" based on the user-provided rq_wqe_shift, which is only checked to be greater than 32, so shifts of 32 are still accepted. A shift of 31 also overflows a signed integer, leading to undefined behavior. Use check_shl_overflow() to compute the RQ WQE size and reject any invalid values.

Affected products

Linux
  • =<5.10.*
  • <4b87a2497276a72fd63028e7419abf0fb7ed837b
  • <d881d60223aac8fdc12b227d89c76e131e92a9cd
  • <42f3d2c8c18b92ea33e506a38b64f1a8986c2823
  • =<6.6.*
  • =<*
  • <9fff54929cc00849d738faa99f06c32399aeb026
  • <6fc874fdfb366bfb11c62e6af9a831c8be59ddda
  • <b732db02a2b04cde393638df19de6251ce62a74e
  • <b746f949c2ac2b041102836095d6d4a2ef21fa75
  • =<6.18.*
  • =<6.12.*
  • =<7.1.*
  • =<5.15.*
  • ==3.11
  • <c1dbf52d24a8cb1aa56780ba51b72e7d495f258c
  • <3.11
  • =<6.1.*
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
wifi: ath12k: fix NULL deref in change_sta_links for unready link

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix NULL deref in change_sta_links for unready link _ieee80211_set_active_links() calls _ieee80211_link_use_channel() for each newly-added link and WARN_ON_ONCE()s if it fails. The call uses assign_on_failure=true, which allows mac80211 to continue despite driver failures, but when a mac80211-level channel validation fails (e.g., combinations check, DFS, or no available radio), drv_assign_vif_chanctx() is never reached. Since ath12k_mac_vdev_create() is only called from that path, arvif->is_created remains false and arvif->ar remains NULL for the failed link. The subsequent drv_change_sta_links() call reaches ath12k_mac_op_change_sta_links(), which allocates an arsta and sets ahsta->links_map |= BIT(link_id) for the broken link before checking whether the link is ready. When the vdev was never created, only station_add() is skipped, but the link remains in links_map. Any subsequent operation iterating links_map and dereferencing arvif->ar without a NULL check will crash. Two observed examples are NULL deref in ath12k_mac_ml_station_remove() on disconnect and in ath12k_mac_op_set_key() when wpa_supplicant installs PTK keys. BUG: Unable to handle kernel NULL pointer dereference at 0x00000000 pc : ath12k_mac_station_post_remove+0x40/0xe8 [ath12k] Call trace: ath12k_mac_station_post_remove+0x40/0xe8 [ath12k] ath12k_mac_op_sta_state+0xb60/0x1720 [ath12k] drv_sta_state+0x100/0xbd8 [mac80211] __sta_info_destroy_part2+0x148/0x178 [mac80211] ieee80211_set_disassoc+0x500/0x678 [mac80211] BUG: Unable to handle kernel NULL pointer dereference at 0x00000000 pc : ath12k_mac_op_set_key+0x1f8/0x2c0 [ath12k] Call trace: ath12k_mac_op_set_key+0x1f8/0x2c0 [ath12k] drv_set_key+0x70/0x100 [mac80211] ieee80211_key_enable_hw_accel+0x78/0x260 [mac80211] ieee80211_add_key+0x16c/0x2ac [mac80211] nl80211_new_key+0x138/0x280 [cfg80211] Fix this by checking arvif->is_created before calling ath12k_mac_alloc_assign_link_sta(). This prevents the broken link from entering links_map, so all subsequent operations iterating the bitmap are protected. The reliability of arvif->is_created across all error paths is ensured by the preceding patch. Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3

Affected products

Linux
  • ==6.14
  • =<*
  • <47809a7c8348bc4a332ccc26a37c7145a5f609f8
  • <5f5be2aa3b6d730c51dd4f8b432f2ad72823e63f
  • =<6.18.*
  • <6.14
  • =<7.1.*
  • <cfcea221db933295bf2cd75a7f80d441c7a51e28
Dismissed
(no matching packages found)
Permalink CVE-2026-16142
9.8 CRITICAL
  • CVSS version (CVSS): 3.1
  • Attack Vector (AV): Network (N)
  • Attack Complexity (AC): Low (L)
  • Privileges Required (PR): None (N)
  • User Interaction (UI): None (N)
  • Scope (S): Unchanged (U)
  • Confidentiality (C): High (H)
  • Integrity (I): High (H)
  • Availability (A): High (H)
  • Modified Attack Vector (MAV): Network (N)
  • Modified Attack Complexity (MAC): Low (L)
  • Modified Privileges Required (MPR): None (N)
  • Modified User Interaction (MUI): None (N)
  • Modified Confidentiality (MC): High (H)
  • Modified Scope (MS): Unchanged (U)
  • Modified Integrity (MI): High (H)
  • Modified Availability (MA): High (H)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (no matching packages found) suggestion
TrueBooker <= 1.2.6 - Unauthenticated Account Takeover via Insecure Direct Object Reference in 'truebooker_wp_user_id' Parameter

The TrueBooker plugin for WordPress is vulnerable to Account Takeover in all versions up to, and including, 1.2.6. This is due to the add_front_user_update() AJAX handler being registered for unauthenticated users and accepting an arbitrary truebooker_wp_user_id value, which is passed directly to wp_update_user() without verifying authentication or ownership. This makes it possible for unauthenticated attackers to change any WordPress user account email address, including an administrator, by submitting the target user ID and an attacker-controlled email address. An attacker can then use the native WordPress password reset flow to receive the reset link at the attacker-controlled email address and take over the account.

Affected products

TrueBooker – Appointment Booking and Scheduler System
  • =<1.2.6
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
ASoC: codecs: hdac_hdmi: Validate written enum value

In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: hdac_hdmi: Validate written enum value hdac_hdmi_set_pin_port_mux() uses the written enum value to index the texts array before calling snd_soc_dapm_put_enum_double(), which validates that the value is within the enum item range. An out-of-range value can therefore make the driver read past the texts array before the helper rejects the write. Move the lookup after the helper has accepted the value.

Affected products

Linux
  • <9131e4b023e0db5764680034bdc94aeae0b0f33d
  • <4.6
  • ==4.6
  • <216336418c007c4b44c650acf2fd3d2de5bb81e8
  • =<6.6.*
  • =<*
  • <0b08baeccdcf52fad328ad645f5b4fbee04eea34
  • <7f02e9064b6f84e7f93c72f134306271eb4f7de4
  • =<6.12.*
  • =<6.18.*
  • <d8961b5c7889b6ecc00f1409d36826df1665df27
  • =<7.1.*
  • =<5.15.*
  • <8cbf24714d6b3f553fc959632c9781176a73a9a7
  • <bc464a6a9e352daa17b1636c090cf3185710b9a0
  • =<6.1.*
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
nvmet-tcp: check return value of nvmet_tcp_set_queue_sock

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock The return value of nvmet_tcp_set_queue_sock() is currently ignored in nvmet_tcp_tls_handshake_done(). If it fails (e.g., due to the socket not being in TCP_ESTABLISHED state), the socket callbacks will not be properly set, leading to queue and socket leakage. Fix this by capturing the return value and calling nvmet_tcp_schedule_release_queue() on failure to ensure proper cleanup.

Affected products

Linux
  • =<*
  • <6.7
  • ==6.7
  • <22aa70f9a0544643ec37d442b6fcb1833d804462
  • =<6.18.*
  • <7ef789703e2b91775dcb36b2efa46325be31a2a0
  • =<7.1.*
  • <cba2ee57fd302727aea7d41e9d9cd0969f5df0fb
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
wifi: mt76: mt7996: Fix possible NULL pointer dereference in mt7996_mac_write_txwi_80211()

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: Fix possible NULL pointer dereference in mt7996_mac_write_txwi_80211() For injected frames (e.g. via radiotap), mac80211 can pass info->control.vif = NULL, as explicitly noted in struct ieee80211_tx_info. Check vif pointer before executing ieee80211_vif_is_mld() in mt7996_mac_write_txwi_80211 routine in order to avoid a possible NULL pointer dereference.

Affected products

Linux
  • <dfb27e5dd9e4d34fbb74fa834c644dcef0be2be9
  • <61370e6674b5253de5686813ceeceebc35a7d3e5
  • =<*
  • ==6.15
  • <6.15
  • =<6.18.*
  • =<7.1.*
  • <63e6151b9791b31877a88ff62806e7c407683955
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
netfilter: nf_conntrack_sip: validate skb_dst() before accessing it

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it tc ingress and openvswitch do not guarantee routing information to be available. These subsystems use the conntrack helper infrastructure, and the SIP helper relies on the skb_dst() to be present if sip_external_media is set to 1 (which is disabled by default as a module parameter). This effectively disables the sip_external_media toggle for these subsystems without resulting in a crash.

Affected products

Linux
  • <b843a96252f672332837ea2ecb7c8db0acf68e20
  • <09755dc62b026076b1d47f83489eb0547c8135e0
  • <c199ed687c00841daf60e9d131976958583a8c09
  • ==4.3
  • =<6.6.*
  • =<*
  • <e64a48c50a1ff565a98c6a98d82b5b942868e76e
  • =<6.18.*
  • =<6.12.*
  • <e5e24a365a5e024efef63cc49abb345fbd4852c5
  • =<7.1.*
  • <4.3
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
Bluetooth: hci_qca: fix NULL pointer dereference in qca_setup() for non-serdev device

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: fix NULL pointer dereference in qca_setup() for non-serdev device hu->serdev is NULL for hci_uart attached via non-serdev paths, but qca_setup() unconditionally calls serdev_device_get_drvdata(hu->serdev) and dereferences the result, causing a NULL pointer dereference. Fix by guarding the dereference with a NULL check, consistent with the rest of qca_setup().

Affected products

Linux
  • =<*
  • <0704c04769ccc1a0939682db35d816dfa5fe75dc
  • ==7.0
  • <7.0
  • =<7.1.*
  • <3ec629fee178d429f01ae843e4ea888de93012bf