p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de linux-oracle-5.15 · Page n° 117

Vulnérabilité publiée pour linux-oracle-5.15 au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

RSS ↗ JSON ↗
Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 4250

  1. CVE-2024-50249

    Moyenne · CVSS 5.5EPSS 0,22%Correctif disponible

    ACPI: CPPC: Make rmw_lock a raw_spin_lock

    In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Make rmw_lock a raw_spin_lock The following BUG was triggered: ============================= [ BUG: Invalid wait context ] 6.12.0-rc2-XXX #406 Not tainted ----------------------------- kworker/1:1/62 is trying to lock: ffffff8801593030 (&cpc_ptr->rmw_lock){+.+.}-{3:3}, at: cpc_write+0xcc/0x370 other info that might help us debug this: context-{5:5} 2 locks held by kworker/1:1/62: #0: ffffff897ef5ec98 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2c/0x50 #1: ffffff880154e238 (&sg_policy->update_lock){....}-{2:2}, at: sugov_update_shared+0x3c/0x280

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  2. CVE-2024-50248

    Élevée · CVSS 7.1EPSS 0,22%Correctif disponible

    ntfs3: Add bounds checking to mi_enum_attr()

    In the Linux kernel, the following vulnerability has been resolved: ntfs3: Add bounds checking to mi_enum_attr() Added bounds checking to make sure that every attr don't stray beyond valid memory region.

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1079.85~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  3. CVE-2024-50247

    Élevée · CVSS 7.3EPSS 0,23%Correctif disponible

    fs/ntfs3: Check if more than chunk-size bytes are written

    In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Check if more than chunk-size bytes are written A incorrectly formatted chunk may decompress into more than LZNT_CHUNK_SIZE bytes and a index out of bounds will occur in s_max_off.

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  5. CVE-2024-50244

    Moyenne · CVSS 5.5EPSS 0,22%Correctif disponible

    fs/ntfs3: Additional check in ni_clear()

    In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Additional check in ni_clear() Checking of NTFS_FLAGS_LOG_REPLAYING added to prevent access to uninitialized bitmap during replay process.

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  7. CVE-2024-50237

    Élevée · CVSS 7.8EPSS 0,27%Correctif disponible

    wifi: mac80211: do not pass a stopped vif to the driver in .get_txpower

    In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: do not pass a stopped vif to the driver in .get_txpower Avoid potentially crashing in the driver because of uninitialized private data

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  8. CVE-2024-50236

    Moyenne · CVSS 5.5EPSS 0,26%Correctif disponible

    wifi: ath10k: Fix memory leak in management tx

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: Fix memory leak in management tx In the current logic, memory is allocated for storing the MSDU context during management packet TX but this memory is not being freed during management TX completion. Similar leaks are seen in the management TX cleanup logic. Kmemleak reports this problem as below, unreferenced object 0xffffff80b64ed250 (size 16): comm "kworker/u16:7", pid 148, jiffies 4294687130 (age 714.199s) hex dump (first 16 bytes): 00 2b d8 d8 80 ff ff ff c4 74 e9 fd 07 00 00 00 .+.......t...... backtrace: [<ffffffe6e7b245dc>] __kmem_cach

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  9. CVE-2024-50234

    Élevée · CVSS 7EPSS 0,19%Correctif disponible

    wifi: iwlegacy: Clear stale interrupts before resuming device

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlegacy: Clear stale interrupts before resuming device iwl4965 fails upon resume from hibernation on my laptop. The reason seems to be a stale interrupt which isn't being cleared out before interrupts are enabled. We end up with a race beween the resume trying to bring things back up, and the restart work (queued form the interrupt handler) trying to bring things down. Eventually the whole thing blows up. Fix the problem by clearing out any stale interrupts before interrupts get enabled during resume. Here's a debug log of the indicent: [ 12.042589] ieee80211 phy

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  10. CVE-2024-50233

    Moyenne · CVSS 5.5EPSS 0,27%Correctif disponible

    staging: iio: frequency: ad9832: fix division by zero in ad9832_calc_freqreg()

    In the Linux kernel, the following vulnerability has been resolved: staging: iio: frequency: ad9832: fix division by zero in ad9832_calc_freqreg() In the ad9832_write_frequency() function, clk_get_rate() might return 0. This can lead to a division by zero when calling ad9832_calc_freqreg(). The check if (fout > (clk_get_rate(st->mclk) / 2)) does not protect against the case when fout is 0. The ad9832_write_frequency() function is called from ad9832_write(), and fout is derived from a text buffer, which can contain any value.

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  11. CVE-2024-50232

    Moyenne · CVSS 5.5EPSS 0,25%Correctif disponible

    iio: adc: ad7124: fix division by zero in ad7124_set_channel_odr()

    In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad7124: fix division by zero in ad7124_set_channel_odr() In the ad7124_write_raw() function, parameter val can potentially be zero. This may lead to a division by zero when DIV_ROUND_CLOSEST() is called within ad7124_set_channel_odr(). The ad7124_write_raw() function is invoked through the sequence: iio_write_channel_raw() -> iio_write_channel_attribute() -> iio_channel_write(), with no checks in place to ensure val is non-zero.

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  12. CVE-2024-50230

    Élevée · CVSS 7.8EPSS 0,28%Correctif disponible

    nilfs2: fix kernel bug due to missing clearing of checked flag

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix kernel bug due to missing clearing of checked flag Syzbot reported that in directory operations after nilfs2 detects filesystem corruption and degrades to read-only, __block_write_begin_int(), which is called to prepare block writes, may fail the BUG_ON check for accesses exceeding the folio/page size, triggering a kernel bug. This was found to be because the "checked" flag of a page/folio was not cleared when it was discarded by nilfs2's own routine, which causes the sanity check of directory entries to be skipped when the directory page/folio is reloaded. So

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  13. CVE-2024-50229

    Moyenne · CVSS 5.5EPSS 0,21%Correctif disponible

    nilfs2: fix potential deadlock with newly created symlinks

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential deadlock with newly created symlinks Syzbot reported that page_symlink(), called by nilfs_symlink(), triggers memory reclamation involving the filesystem layer, which can result in circular lock dependencies among the reader/writer semaphore nilfs->ns_segctor_sem, s_writers percpu_rwsem (intwrite) and the fs_reclaim pseudo lock. This is because after commit 21fc61c73c39 ("don't put symlink bodies in pagecache into highmem"), the gfp flags of the page cache for symbolic links are overwritten to GFP_KERNEL via inode_nohighmem(). This is not a problem f

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  14. CVE-2024-50218

    Moyenne · CVSS 6.9EPSS 0,27%Correctif disponible

    ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow

    In the Linux kernel, the following vulnerability has been resolved: ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow Syzbot reported a kernel BUG in ocfs2_truncate_inline. There are two reasons for this: first, the parameter value passed is greater than ocfs2_max_inline_data_with_xattr, second, the start and end parameters of ocfs2_truncate_inline are "unsigned int". So, we need to add a sanity check for byte_start and byte_len right before ocfs2_truncate_inline() in ocfs2_remove_inode_range(), if they are greater than ocfs2_max_inline_data_with_xattr return -EINVAL.

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  16. CVE-2024-50209

    Élevée · CVSS 7.8EPSS 0,21%Correctif disponible

    RDMA/bnxt_re: Add a check for memory allocation

    In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Add a check for memory allocation __alloc_pbl() can return error when memory allocation fails. Driver is not checking the status on one of the instances.

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  17. CVE-2024-50208

    Élevée · CVSS 7.8EPSS 0,23%Correctif disponible

    RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages

    In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages Avoid memory corruption while setting up Level-2 PBL pages for the non MR resources when num_pages > 256K. There will be a single PDE page address (contiguous pages in the case of > PAGE_SIZE), but, current logic assumes multiple pages, leading to invalid memory access after 256K PBL entries in the PDE.

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  18. CVE-2024-50205

    Moyenne · CVSS 5.5EPSS 0,23%Correctif disponible

    ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size()

    In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() The step variable is initialized to zero. It is changed in the loop, but if it's not changed it will remain zero. Add a variable check before the division. The observed behavior was introduced by commit 826b5de90c0b ("ALSA: firewire-lib: fix insufficient PCM rule for period/buffer size"), and it is difficult to show that any of the interval parameters will satisfy the snd_interval_test() condition with data from the amdtp_rate_table[] table. Found by Linux Verification Center (linuxtesting.org) with

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  19. CVE-2024-50202

    Moyenne · CVSS 5.5EPSS 0,23%Correctif disponible

    nilfs2: propagate directory read errors from nilfs_find_entry()

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: propagate directory read errors from nilfs_find_entry() Syzbot reported that a task hang occurs in vcs_open() during a fuzzing test for nilfs2. The root cause of this problem is that in nilfs_find_entry(), which searches for directory entries, ignores errors when loading a directory page/folio via nilfs_get_folio() fails. If the filesystem images is corrupted, and the i_size of the directory inode is large, and the directory page/folio is successfully read but fails the sanity check, for example when it is zero-filled, nilfs_check_folio() may continue to spit out

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  20. CVE-2024-50201

    Moyenne · CVSS 5.5EPSS 0,21%Correctif disponible

    drm/radeon: Fix encoder->possible_clones

    In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Fix encoder->possible_clones Include the encoder itself in its possible_clones bitmask. In the past nothing validated that drivers were populating possible_clones correctly, but that changed in commit 74d2aacbe840 ("drm: Validate encoder->possible_clones"). Looks like radeon never got the memo and is still not following the rules 100% correctly. This results in some warnings during driver initialization: Bogus possible_clones: [ENCODER:46:TV-46] possible_clones=0x4 (full encoder mask=0x7) WARNING: CPU: 0 PID: 170 at drivers/gpu/drm/drm_mode_config.c:615 drm_mod

    linux-oracle-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1075.81~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →