Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2024-4992 State: PUBLISHED Published: 2024-05-16T11:43:19.292Z Last Updated: 2024-08-01T20:55:10.415Z Severity: CRITICAL (CVSS 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) Vendors: SiAdmin Products: SiAdmin Problem Types: CWE-89 Description: Vulnerability in SiAdmin 1.1 that allows SQL injection via the /modul/mod_kuliah/aksi_kuliah.php parameter in nim. This vulnerability could allow a remote attacker to send a specially crafted SQL query to the system and retrieve all the information stored in it. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-siadmin
CVE ID: CVE-2024-4993 State: PUBLISHED Published: 2024-05-16T11:44:47.582Z Last Updated: 2024-08-01T20:55:10.414Z Severity: MEDIUM (CVSS 6.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L) Vendors: SiAdmin Products: SiAdmin Problem Types: CWE-79 Description: Vulnerability in SiAdmin 1.1 that allows XSS via the /show.php query parameter. This vulnerability could allow a remote attacker to send a specially crafted URL to an authenticated user and thereby steal their cookie session credentials. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-siadmin
CVE ID: CVE-2024-4994 State: PUBLISHED Published: 2025-06-20T18:14:37.887Z Last Updated: 2025-06-23T15:22:37.297Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) Vendors: GitLab Products: GitLab Problem Types: CWE-352 Description: An issue has been discovered in GitLab CE/EE affecting all versions from 16.1.0 before 16.11.5, all versions starting from 17.0 before 17.0.3, all versions starting from 17.1.0 before 17.1.1 which allowed for a CSRF attack on GitLab's GraphQL API leading to the execution of arbitrary GraphQL mutations. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://gitlab.com/gitlab-org/gitlab/-/issues/462012 - https://hackerone.com/
es: - CISA ADP Vulnrichment: References: - https://gitlab.com/gitlab-org/gitlab/-/issues/462012 - https://hackerone.com/reports/2473644
CVE ID: CVE-2024-4995 State: PUBLISHED Published: 2024-12-18T11:36:47.588Z Last Updated: 2025-10-07T13:20:30.088Z Vendors: Asseco Business Solutions S.A. Products: Wapro ERP Desktop Problem Types: CWE-757 Description: Wapro ERP Desktop is vulnerable to MS SQL protocol downgrade request from a server side, what could lead to an unencrypted communication vulnerable to data interception and modification. This issue affects Wapro ERP Desktop versions before 9.00.0. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://cert.pl/en/posts/2024/12/CVE-2024-4995/ - https://cert.pl/posts/2024/12/CVE-2024-4995/ - https://wapro.pl/
CVE ID: CVE-2024-4996 State: PUBLISHED Published: 2024-12-18T11:37:23.937Z Last Updated: 2025-10-07T13:21:35.535Z Vendors: Asseco Business Solutions S.A. Products: Wapro ERP Desktop Problem Types: CWE-259 Description: Use of a hard-coded password for a database administrator account created during Wapro ERP installation allows an attacker to retrieve embedded sensitive data stored in the database. The password is same among all Wapro ERP installations. This issue affects Wapro ERP Desktop versions before 8.90.0. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://cert.pl/en/posts/2024/12/CVE-2024-4995/ - https://cert.pl/posts/2024/12/CVE-2024-4995/ - https://wapro.pl/
CVE ID: CVE-2024-4997 State: PUBLISHED Published: 2024-06-04T05:32:17.102Z Last Updated: 2024-08-01T20:55:10.436Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Vendors: victorfreitas Products: WPUpper Share Buttons Problem Types: CWE-862 Missing Authorization Description: The WPUpper Share Buttons plugin for WordPress is vulnerable to unauthorized access of data when preparing sharing links for posts and pages in all versions up to, and including, 3.43. This makes it possible for unauthenticated attackers to obtain the contents of password protected posts and pages. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://ww
ed posts and pages. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://www.wordfence.com/threat-intel/vulnerabilities/id/c68ec00c-20a5-461d-bf72-c3190d29c9cf?source=cve - https://wordpress.org/plugins/wpupper-share-buttons/
CVE ID: CVE-2024-4998 State: REJECTED Published: N/A Last Updated: 2024-05-17T15:44:44.397Z Description: No description available.
CVE ID: CVE-2024-4999 State: PUBLISHED Published: 2024-05-16T12:14:51.671Z Last Updated: 2024-08-01T20:55:10.386Z Vendors: Ligowave Products: UNITY, PRO, MIMO, APC Propeller Problem Types: CWE-77 Description: A vulnerability in the web-based management interface of multiple Ligowave devices could allow an authenticated remote attacker to execute arbitrary commands with elevated privileges.This issue affects UNITY: through 6.95-2; PRO: through 6.95-1.Rt3883; MIMO: through 6.95-1.Rt2880; APC Propeller: through 2-5.95-4.Rt3352. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://onekey.com/blog/security-advisory-remote-code-execution-in-ligowave-dev
: - CVE Program Container: References: - https://onekey.com/blog/security-advisory-remote-code-execution-in-ligowave-devices/
CVE ID: CVE-2024-50000 State: PUBLISHED Published: 2024-10-21T18:02:39.600Z Last Updated: 2025-11-03T22:24:16.040Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() In mlx5e_tir_builder_alloc() kvzalloc() may return NULL which is dereferenced on the next line in a reference to the modify field. Found by Linux Verification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/4655456a64a0f936098c8432bac64e7176bd2aff - https://git.kernel.org/stable/c/b48ee5bb25c02ca2b81e0d16
.kernel.org/stable/c/4655456a64a0f936098c8432bac64e7176bd2aff - https://git.kernel.org/stable/c/b48ee5bb25c02ca2b81e0d16bf8af17ab6ed3f8b - https://git.kernel.org/stable/c/0168ab6fbd9e50d20b97486168b604b2ab28a2ca - https://git.kernel.org/stable/c/1bcc86cc721bea68980098f51f102aa2c2b9d932 - https://git.kernel.org/stable/c/4d80dde26d7bab1320210279483ac854dcb274b2 - https://git.kernel.org/stable/c/f25389e779500cf4a59ef9804534237841bce536
CVE ID: CVE-2024-50001 State: PUBLISHED Published: 2024-10-21T18:02:40.254Z Last Updated: 2025-11-03T22:24:17.517Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix error path in multi-packet WQE transmit Remove the erroneous unmap in case no DMA mapping was established The multi-packet WQE transmit code attempts to obtain a DMA mapping for the skb. This could fail, e.g. under memory pressure, when the IOMMU driver just can't allocate more memory for page tables. While the code tries to handle this in the path below the err_unmap label it erroneously unmaps one entry from the sq's FIFO list of active mappings. Since
in the path below the err_unmap label it erroneously unmaps one entry from the sq's FIFO list of active mappings. Since the current map attempt failed this unmap is removing some random DMA mapping that might still be required. If the PCI function now presents that IOVA, the IOMMU may assumes a rogue DMA access and e.g. on s390 puts the PCI function in error state. The erroneous behavior was seen in a stress-test environment that created memory pressure. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/ca36d6c1a49b6965c86dd528a73f38bc62d9c625 - https://git.kernel.org/stable/c/ce828b347cf1b3c1b12b091d02463c35ce5097f5 - h
/ca36d6c1a49b6965c86dd528a73f38bc62d9c625 - https://git.kernel.org/stable/c/ce828b347cf1b3c1b12b091d02463c35ce5097f5 - https://git.kernel.org/stable/c/fc357e78176945ca7bcacf92ab794b9ccd41b4f4 - https://git.kernel.org/stable/c/26fad69b34fcba80d5c7d9e651f628e6ac927754 - https://git.kernel.org/stable/c/ecf310aaf256acbc8182189fe0aa1021c3ddef72 - https://git.kernel.org/stable/c/8bb8c12fb5e2b1f03d603d493c92941676f109b5 - https://git.kernel.org/stable/c/2bcae12c795f32ddfbf8c80d1b5f1d3286341c32
CVE ID: CVE-2024-50002 State: PUBLISHED Published: 2024-10-21T18:02:40.908Z Last Updated: 2025-11-03T22:24:18.968Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: static_call: Handle module init failure correctly in static_call_del_module() Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain. If that allocation fails the function returns
further modules can be added or to append the module to the module chain. If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries. This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod. The problem is that key::mods is not a individual struct member of struct static_call_key, it's part of a union to save space: union { /* bit 0: 0 = mods, 1 = sites */ unsigned long type; struct static_call_mod
it's part of a union to save space: union { /* bit 0: 0 = mods, 1 = sites */ unsigned long type; struct static_call_mod *mods; struct static_call_site *sites; }; key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set. As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus. Cure it by checking whether the key has a sites or a mods pointer. If it's a sites pointer then the key is not to
bogus. Cure it by checking whether the key has a sites or a mods pointer. If it's a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit. If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing. A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner
eded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can't match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/ed4c8ce0f307f2ab8778aeb40a8866d171e8f128 - https://git.kernel.org/stable/c/b566c7d8a2de403ccc9d8a06195e19bbb386d0e4 - https://git.kernel.org/stable/c/c0abbbe8c98c077292221ec7e2baa6
l.org/stable/c/b566c7d8a2de403ccc9d8a06195e19bbb386d0e4 - https://git.kernel.org/stable/c/c0abbbe8c98c077292221ec7e2baa667c9f0974c - https://git.kernel.org/stable/c/2b494471797bff3d257e99dc0a7abb0c5ff3b4cd - https://git.kernel.org/stable/c/9c48c2b53191bf991361998f5bb97b8f2fc5a89c - https://git.kernel.org/stable/c/4b30051c4864234ec57290c3d142db7c88f10d8a
CVE ID: CVE-2024-50003 State: PUBLISHED Published: 2024-10-21T18:53:57.938Z Last Updated: 2025-11-03T22:24:20.447Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix system hang while resume with TBT monitor [Why] Connected with a Thunderbolt monitor and do the suspend and the system may hang while resume. The TBT monitor HPD will be triggered during the resume procedure and call the drm_client_modeset_probe() while struct drm_connector connector->dev->master is NULL. It will mess up the pipe topology after resume. [How] Skip the TBT monitor HPD during the resume procedure because we currently will probe the co
topology after resume. [How] Skip the TBT monitor HPD during the resume procedure because we currently will probe the connectors after resume by default. (cherry picked from commit 453f86a26945207a16b8f66aaed5962dc2b95b85) Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/eb9329cd882aa274e92bdb1003bc088433fdee86 - https://git.kernel.org/stable/c/722d2d8fc423108597b97efbf165187d16d9aa1e - https://git.kernel.org/stable/c/68d603f467a75618eeae5bfe8af32cda47097010 - https://git.kernel.org/stable/c/73e441be033d3ed0bdff09b575da3e7d4606ffc9 - https://git.kernel.org/stable/c/c2356296f546326f9f06c109e201d42201e1e783 - https://git.
3d3ed0bdff09b575da3e7d4606ffc9 - https://git.kernel.org/stable/c/c2356296f546326f9f06c109e201d42201e1e783 - https://git.kernel.org/stable/c/52d4e3fb3d340447dcdac0e14ff21a764f326907
CVE ID: CVE-2024-50004 State: PUBLISHED Published: 2024-10-21T18:53:58.609Z Last Updated: 2025-05-04T09:43:34.511Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: update DML2 policy EnhancedPrefetchScheduleAccelerationFinal DCN35 [WHY & HOW] Mismatch in DCN35 DML2 cause bw validation failed to acquire unexpected DPP pipe to cause grey screen and system hang. Remove EnhancedPrefetchScheduleAccelerationFinal value override to match HW spec. (cherry picked from commit 9dad21f910fcea2bdcff4af46159101d7f9cd8ba) Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/945dc25eda
01d7f9cd8ba) Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/945dc25eda88b5d6e30c9686dc619ab981c22d0e - https://git.kernel.org/stable/c/4010efc8516899981cc3b57be2d4a2d5d9e50228 - https://git.kernel.org/stable/c/0d5e5e8a0aa49ea2163abf128da3b509a6c58286
CVE ID: CVE-2024-50005 State: PUBLISHED Published: 2024-10-21T18:53:59.259Z Last Updated: 2025-05-04T09:43:36.186Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mac802154: Fix potential RCU dereference issue in mac802154_scan_worker In the `mac802154_scan_worker` function, the `scan_req->type` field was accessed after the RCU read-side critical section was unlocked. According to RCU usage rules, this is illegal and can lead to unpredictable behavior, such as accessing memory that has been updated or causing use-after-free issues. This possible bug was identified using a static analysis tool developed by myself, specifically de
se-after-free issues. This possible bug was identified using a static analysis tool developed by myself, specifically designed to detect RCU-related issues. To address this, the `scan_req->type` value is now stored in a local variable `scan_req_type` while still within the RCU read-side critical section. The `scan_req_type` is then used after the RCU lock is released, ensuring that the type value is safely accessed without violating RCU rules. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/e676e4ea76bbe7f1156d8c326b9b6753849481c2 - https://git.kernel.org/stable/c/540138377b22f601f06f55ebfa3ca171dcab471a - https://git.kernel.org/stable/c/d18f6
481c2 - https://git.kernel.org/stable/c/540138377b22f601f06f55ebfa3ca171dcab471a - https://git.kernel.org/stable/c/d18f669461811dfe2915d5554ab2a9834f810013 - https://git.kernel.org/stable/c/bff1709b3980bd7f80be6786f64cc9a9ee9e56da
CVE ID: CVE-2024-50006 State: PUBLISHED Published: 2024-10-21T18:53:59.938Z Last Updated: 2025-11-03T22:24:21.923Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ext4: fix i_data_sem unlock order in ext4_ind_migrate() Fuzzing reports a possible deadlock in jbd2_log_wait_commit. This issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require synchronous updates because the file descriptor is opened with O_SYNC. This can lead to the jbd2_journal_stop() function calling jbd2_might_wait_for_commit(), potentially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2) system call. This problem only arises when
ntially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2) system call. This problem only arises when CONFIG_PROVE_LOCKING is enabled. In this case, the jbd2_might_wait_for_commit macro locks jbd2_handle in the jbd2_journal_stop function while i_data_sem is locked. This triggers lockdep because the jbd2_journal_start function might also lock the same jbd2_handle simultaneously. Found by Linux Verification Center (linuxtesting.org) with syzkaller. Rule: add Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/4192adefc9c570698821c5eb9873320eac2fcbf1 - https://git.kernel.org/stable/c/3c46d6060d3e38de22196c1
t.kernel.org/stable/c/4192adefc9c570698821c5eb9873320eac2fcbf1 - https://git.kernel.org/stable/c/3c46d6060d3e38de22196c1fe7706c5a3c696285 - https://git.kernel.org/stable/c/53b1999cfd2c7addf2e581a32865fe8835467b44 - https://git.kernel.org/stable/c/ef05572da0c0eb89614ed01cc17d3c882bdbd1ff - https://git.kernel.org/stable/c/9fedf51ab8cf7b69bff08f37fe0989fec7f5d870 - https://git.kernel.org/stable/c/d43776b907659affef1de888525847d64b244194 - https://git.kernel.org/stable/c/6252cb6bde7fc76cb8dcb49d1def7c326b190820 - https://git.kernel.org/stable/c/d58a00e981d3118b91d503da263e640b7cde6729 - https://git.kernel.org/stable/c/cc749e61c011c255d81b192a822db650c68b313f
CVE ID: CVE-2024-50007 State: PUBLISHED Published: 2024-10-21T18:54:00.611Z Last Updated: 2025-11-03T22:24:23.381Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ALSA: asihpi: Fix potential OOB array access ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware. We shouldn't trust it blindly. This patch adds a sanity check of the array index to fit in the array size. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/a6bdb691cf7b66dcd929de1a253c5c42edd2e522 - https://git.kernel.org/stable/c
References: - https://git.kernel.org/stable/c/a6bdb691cf7b66dcd929de1a253c5c42edd2e522 - https://git.kernel.org/stable/c/ce2953e44829ec54bcbb57e9d890fc8af0900c80 - https://git.kernel.org/stable/c/219587bca2678e31700ef09ecec178ba1f735674 - https://git.kernel.org/stable/c/36ee4021bcc37b834996e79740d095d6f8dd948f - https://git.kernel.org/stable/c/e658227d9d4f4e122d81690fdbc0d438b10288f5 - https://git.kernel.org/stable/c/7a55740996701f7b2bc46dc988b60ef2e416a747 - https://git.kernel.org/stable/c/ad7248a5e92587b9266c62db8bcc4e58de53e372 - https://git.kernel.org/stable/c/876d04bf5a8ac1d6af5afd258cd37ab83ab2cf3d - https://git.kernel.org/stable/c/7b986c7430a6bb68d523dac7bfc74cbd5b44ef96
CVE ID: CVE-2024-50008 State: PUBLISHED Published: 2024-10-21T18:54:01.348Z Last Updated: 2025-11-03T22:24:24.839Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`. With this, fix the following warning: elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field "ext_scan->tlv_buffer" at drivers/net/wireless/marvell/mwifiex/scan.c:2239
ld-spanning write (size 243) of single field "ext_scan->tlv_buffer" at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex] Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/b55c8848fdc81514ec047b2a0ec782ffe9ab5323 - https://git.kernel.org/stable/c/f9310a6704bf52e2493480edea896e1f9b795d40 - https://git.kernel.org/stable/c/1756918f51e9ab247a0f4782cc28853c2bb457c1 - https://git.kernel.org/stable/c/e59bdb1ba594104cd0ee0af3ee9e4435d842a8fe - https://git.kernel.o
0f4782cc28853c2bb457c1 - https://git.kernel.org/stable/c/e59bdb1ba594104cd0ee0af3ee9e4435d842a8fe - https://git.kernel.org/stable/c/17199b69a84798efffc475040fbef44374ef1de1 - https://git.kernel.org/stable/c/fef7b51f22cf2049b0ca6740adeb0ba6f2e671dc - https://git.kernel.org/stable/c/71267bd4e8c752d7af6c6b96bb83984a6a95273d - https://git.kernel.org/stable/c/a3a12c30f9510f3753286fadbc6cdb7dad78c1d5 - https://git.kernel.org/stable/c/498365e52bebcbc36a93279fe7e9d6aec8479cee
CVE ID: CVE-2024-50009 State: PUBLISHED Published: 2024-10-21T18:54:02.180Z Last Updated: 2025-05-04T09:43:42.257Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value cpufreq_cpu_get may return NULL. To avoid NULL-dereference check it and return in case of error. Found by Linux Verification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/cd9f7bf6cad8b2d3876105ce3c9fc63460a046f6 - https://git.kernel.org/stable/c/5f250d44b8191d612355dd97b89b37bbc1b5d2cb - https://git.kernel.org/stable
fc63460a046f6 - https://git.kernel.org/stable/c/5f250d44b8191d612355dd97b89b37bbc1b5d2cb - https://git.kernel.org/stable/c/5493f9714e4cdaf0ee7cec15899a231400cb1a9f
CVE ID: CVE-2024-50010 State: PUBLISHED Published: 2024-10-21T18:54:02.974Z Last Updated: 2025-11-03T22:24:26.304Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: exec: don't WARN for racy path_noexec check Both i_mode and noexec checks wrapped in WARN_ON stem from an artifact of the previous implementation. They used to legitimately check for the condition, but that got moved up in two commits: 633fb6ac3980 ("exec: move S_ISREG() check earlier") 0fd338b2d2cd ("exec: move path_noexec() check earlier") Instead of being removed said checks are WARN_ON'ed instead, which has some debug value. However, the spurious path_noexec check
f being removed said checks are WARN_ON'ed instead, which has some debug value. However, the spurious path_noexec check is racy, resulting in unwarranted warnings should someone race with setting the noexec flag. One can note there is more to perm-checking whether execve is allowed and none of the conditions are guaranteed to still hold after they were tested for. Additionally this does not validate whether the code path did any perm checking to begin with -- it will pass if the inode happens to be regular. Keep the redundant path_noexec() check even though it's mindless nonsense checking for guarantee that isn't given so drop the WARN. Reword the commentary and do small tidy ups while here.