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: seq: midi: Serialize output teardown with event_input

In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: midi: Serialize output teardown with event_input event_process_midi() borrows msynth->output_rfile.output and then passes the substream to dump_midi() and snd_rawmidi_kernel_write() without synchronizing with the output open/close transition. midisynth_use() also publishes output_rfile before snd_rawmidi_output_params() has finished. The last midisynth_unuse() can therefore release the same rawmidi file and free substream->runtime before snd_rawmidi_kernel_write1() takes its runtime buffer reference. That leaves the event_input path using a stale substream or runtime and can end in a NULL-deref or use-after-free. Fix this with two pieces of synchronization. Keep a short IRQ-safe spinlock only for publishing or clearing output_rfile and for pairing the output snapshot with an snd_use_lock_t reference. Once event_process_midi() has taken that in-flight reference, it drops the spinlock before calling snd_seq_dump_var_event(), dump_midi(), or snd_rawmidi_kernel_write(). midisynth_unuse() now detaches the visible rawmidi file under the same spinlock, waits for the in-flight writers to drain, and only then drains and releases the saved file. midisynth_use() likewise opens into a local snd_rawmidi_file and publishes it only after snd_rawmidi_output_params() succeeds. The buggy scenario involves two paths, with each column showing the order within that path: event_input path: last unuse path: 1. event_process_midi() snapshots 1. midisynth_unuse() starts output_rfile.output. tearing down output_rfile. 2. dump_midi() reaches 2. snd_rawmidi_kernel_release() snd_rawmidi_kernel_write() closes the output file. before runtime is pinned. 3. close_substream() frees 3. The callback keeps using substream->runtime. the borrowed substream. Validation reproduced this kernel report: KASAN null-ptr-deref in snd_rawmidi_kernel_write1+0x56/0x360 RIP: 0033:0x7fde7dd0837f RIP: 0010:snd_rawmidi_kernel_write1+0x56/0x360

Affected products

Linux
  • <11165fe2c5ea0516debe486d91df67abbe36905e
  • <f5d470b808bc01f70978e22e595c6f7768313406
  • =<6.6.*
  • =<*
  • <936641af564c3d92721704b781e36aaf223efdd2
  • =<6.18.*
  • =<6.12.*
  • <d6fd2afb137f52bf00c5210cc44d08ed54dcffb4
  • <2.6.12
  • =<7.1.*
  • ==2.6.12
  • <718f6a56b40875f19e6915799044a02df9abfd52
  • <ef7607ab1c8adc6258fb1b27d08e26aecdc18a58
  • =<6.1.*
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
netfilter: nf_dup_netdev: add nf_dev_xmit_recursion*() helpers and use them

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_dup_netdev: add nf_dev_xmit_recursion*() helpers and use them Update nft_dup and nft_fwd to use the nf_dev_xmit_recursion() helpers. This patch also disables BH when transmitting the skb to address a possible migration to different CPU leading to imbalanced decrementation of the recursion counters. This is modeled after Florian Westphal's dev_xmit_recursion*() API available since commit 97cdcf37b57e ("net: place xmit recursion in softnet data") according to its current state in the tree.

Affected products

Linux
  • ==6.16
  • <6.16
  • =<*
  • =<7.1.*
  • <edf234f71fb327792196f813048ab8f5bd3bb712
  • <2354e975932dabb06fad239f07a3b68fd1809737
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
net: dsa: sja1105: round up PTP perout pin duration

In the Linux kernel, the following vulnerability has been resolved: net: dsa: sja1105: round up PTP perout pin duration pin_duration is converted from the user-provided period to SJA1105 clock ticks and is later passed as the cycle_time argument to future_base_time(). Very small period values may become zero after the conversion, which can lead to a division by zero in future_base_time(). Round zero pin_duration up to 1 tick so that the smallest unsupported periods use the minimum non-zero hardware duration instead of passing zero to future_base_time().

Affected products

Linux
  • ==5.7
  • <aee5836273b07b439fb245fb43930664d8b78518
  • =<5.10.*
  • =<6.6.*
  • =<*
  • <5.7
  • <201dcbbfb27f3db85c8cf125a75f3164a83ceb32
  • <aaf446099ca497c8d9a8e511fedf5d0e547bf8ec
  • <410629528067029096dba7ad7bc49e4a5e92708d
  • =<6.12.*
  • <fc62bfd30d30af07356f0f7121c826e1e753582f
  • <09efce96c909dff1a9317ec3714b7ddb4751b7af
  • =<6.18.*
  • =<7.1.*
  • =<5.15.*
  • =<6.1.*
  • <28d13a89a211cc07caeef32069eaa847131b7351
  • <9952291db7125b8a62bf19800b93dcac81fc70c0
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
apparmor: fail policy unpack on accept2 allocation failure

In the Linux kernel, the following vulnerability has been resolved: apparmor: fail policy unpack on accept2 allocation failure unpack_pdb() may need to allocate a missing ACCEPT2 table for older policy data. If that allocation failed, it set an error message but jumped to the success path, returning a policydb with the required table missing. Return -ENOMEM through the normal failure path when the ACCEPT2 allocation fails. Remove the now-unused out label.

Affected products

Linux
  • <106e909e12baf059538f0b0f1a59f87781d25b3c
  • <6.17
  • ==6.17
  • =<*
  • <45cf568241048e560a81aa2053f06a62069f5640
  • <22dc9433d458cff1270f120685114a9753e0ad1b
  • =<6.18.*
  • =<7.1.*
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
fbdev: nvidia: fix potential memory leak in nvidiafb_probe()

In the Linux kernel, the following vulnerability has been resolved: fbdev: nvidia: fix potential memory leak in nvidiafb_probe() In nvidiafb_probe(), the memory allocated for modelist in nvidia_set_fbinfo() is not freed in the subsequent error paths. Fix that by calling fb_destroy_modelist().

Affected products

Linux
  • <7e747f7b17ccce750502fd4d0b4e866fe4f066a6
  • <e8172773e5251f4df2eed74caab6ca3195fed1ea
  • <009a8514745b16c468acc25aa00539abbf38e1b5
  • =<5.10.*
  • <85f5e38c162bdf9dbbe197275d416402712f3707
  • <6ca48f23ce61a26349d7d084fb63b70499137c8e
  • <508704de34fb8c0dcbbf13397212363bbf0974de
  • =<6.6.*
  • =<*
  • <ed3b3eb212441fb5f287dfd24ebafe11d634f009
  • =<6.18.*
  • =<6.12.*
  • <2515cd60f6b5ad680ed164aa6bd19b05270af34c
  • <2.6.12
  • =<5.15.*
  • ==2.6.12
  • =<7.1.*
  • =<6.1.*
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
ntfs: harden runlist realloc size calculations

In the Linux kernel, the following vulnerability has been resolved: ntfs: harden runlist realloc size calculations Add a shared helper to safely convert runlist element counts to byte sizes using overflow checks, and use it in both ntfs_rl_realloc() and ntfs_rl_realloc_nofail().

Affected products

Linux
  • =<*
  • <7.1
  • =<7.1.*
  • ==7.1
  • <8bed376124ab4505b70083a2b91f2c7ef6d51e24
  • <57e7b8bf7b02a0140463fea786e5172cbdf2da2f
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
net/liquidio: drop cached VF pci_dev LUT

In the Linux kernel, the following vulnerability has been resolved: net/liquidio: drop cached VF pci_dev LUT The PF SR-IOV enable path caches VF pci_dev pointers in dpiring_to_vfpcidev_lut[] by iterating with pci_get_device(). Those entries do not own a reference, because the iterator drops the previous device reference on each step. The cached pointer is then dereferenced later when handling OCTEON_VF_FLR_REQUEST. Replace the cached VF mapping with runtime lookup on the mailbox DPI ring: derive the VF index from q_no, resolve the VF via exported PCI IOV helpers, validate it with the PF pointer and VF ID, then issue pcie_flr() and drop the reference with pci_dev_put(). Remove the unused VF lookup table initialization and cleanup.

Affected products

Linux
  • <5c0e3ba4f500fd4314ceb42f07f16bc445156431
  • =<*
  • <4.10
  • ==4.10
  • =<7.1.*
  • <81acef3a247fd523513a2e9f71de1c167bc0f882
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
ata: libata-core: Add NOLPM quirk for PNY CS900 1TB SSD

In the Linux kernel, the following vulnerability has been resolved: ata: libata-core: Add NOLPM quirk for PNY CS900 1TB SSD The PNY CS900 1TB SSD (Phison PS3111-S11, DRAM-less) drops off the bus after entering Device-Initiated Slumber during idle. With the default med_power_with_dipm policy the link goes down (SStatus 1 SControl 300) and does not recover, forcing the filesystem read-only. Forcing max_performance keeps the link stable across prolonged idle. Add a NOLPM quirk so link power management is disabled for this drive specifically, leaving it intact for other devices on the host.

Affected products

Linux
  • =<*
  • <7.1.5
  • =<7.1.*
  • <299739909c486bcea7445f5c3b066fdbc0d2df96
  • <462775c620197adaabc983ce847e5b9878ff4cb0
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
alloc_tag: fix use-after-free in /proc/allocinfo after module unload

In the Linux kernel, the following vulnerability has been resolved: alloc_tag: fix use-after-free in /proc/allocinfo after module unload allocinfo_start() only reinitializes the codetag iterator at position 0. For subsequent reads (position > 0), it reuses cached iterator state from the previous batch. allocinfo_stop() drops mod_lock between read batches, which allows module unload to complete and free the module memory that the cached iterator still references: CPU0 (read) CPU1 (rmmod) ---- ---- allocinfo_start(pos=0) down_read(mod_lock) allocinfo_show() ... allocinfo_stop() up_read(mod_lock) codetag_unload_module() kfree(cmod) release_module_tags() ... free_mod_mem() allocinfo_start(pos=N) down_read(mod_lock) // reuses cached iter, skips re-init allocinfo_show() ct->filename <-- UAF After free_mod_mem() frees the module's .rodata, allocinfo_show() dereferences ct->filename, ct->function which point there. Save the iterator state in allocinfo_next() and resume from it in allocinfo_start() with codetag_next_ct(), which detects module removal via idr_find() returning NULL and skips to the next module.

Affected products

Linux
  • <008ceffd44040f809aead6d7bef7cb1210c4149a
  • <6.17
  • <37e3e8a2c3bfdd503209f043f8bbfbdcf5a1d92f
  • ==6.17
  • =<*
  • =<6.18.*
  • <2956268efc457cb05d29c1bf94de1e8e684d7bbc
  • =<7.1.*
Dismissed
(max. allowed matches exceeded)
created 3 weeks, 4 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
s390/qeth: Check CAP_NET_ADMIN for private ioctls

In the Linux kernel, the following vulnerability has been resolved: s390/qeth: Check CAP_NET_ADMIN for private ioctls Gate the SIOCDEVPRIVATE ioctl commands SIOC_QETH_ADP_SET_SNMP_CONTROL, SIOC_QETH_GET_CARD_TYPE and SIOC_QETH_QUERY_OAT with CAP_NET_ADMIN capable check to ensure unprivileged users cannot invoke them.

Affected products

Linux
  • <5.15
  • =<*
  • <b40c74262f7e1e601221cebccdbdb2b392ff9976
  • =<6.6.*
  • <bd63c7879eaa87f1958f7ee027813356fcd9ff11
  • ==5.15
  • <4e48168825818bf4a13c743582227d15f1d30d04
  • <d211028bac1bd0fff0026bfa2a8328e5b78cd0e6
  • =<6.12.*
  • =<6.18.*
  • =<7.1.*
  • <93a0a846ec59a88e0c402878a15357a5ce430eb4