Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
ait for BH work items that are being canceled. While the read is safe when @from_cancel, @work->data was read before testing @from_cancel to simplify code structure: data = *work_data_bits(work); if (from_cancel && !WARN_ON_ONCE(data & WORK_STRUCT_PWQ) && (data & WORK_OFFQ_BH)) { While the read data was never used if !@from_cancel, this could trigger KCSAN data race detection spuriously: ================================================================== BUG: KCSAN: data-race in __flush_work / __flush_work write to 0xffff8881223aa3e8 of 8 bytes by task 3998 on cpu 0: instrument_write include/linux/instrumented.h:41 [inline] ___set_bit include/asm-generic/bitops/instrumented-non-atomic.h:28 [i
ent_write include/linux/instrumented.h:41 [inline] ___set_bit include/asm-generic/bitops/instrumented-non-atomic.h:28 [inline] insert_wq_barrier kernel/workqueue.c:3790 [inline] start_flush_work kernel/workqueue.c:4142 [inline] __flush_work+0x30b/0x570 kernel/workqueue.c:4178 flush_work kernel/workqueue.c:4229 [inline] ... read to 0xffff8881223aa3e8 of 8 bytes by task 50 on cpu 1: __flush_work+0x42a/0x570 kernel/workqueue.c:4188 flush_work kernel/workqueue.c:4229 [inline] flush_delayed_work+0x66/0x70 kernel/workqueue.c:4251 ... value changed: 0x0000000000400000 -> 0xffff88810006c00d Reorganize the code so that @from_cancel is tested before @work->data is accessed. The only problem is trigger
10006c00d Reorganize the code so that @from_cancel is tested before @work->data is accessed. The only problem is triggering KCSAN detection spuriously. This shouldn't need READ_ONCE() or other access qualifiers. No functional changes. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/91d09642127a32fde231face2ff489af70eef316 - https://git.kernel.org/stable/c/8bc35475ef1a23b0e224f3242eb11c76cab0ea88
CVE ID: CVE-2024-46705 State: PUBLISHED Published: 2024-09-13T06:27:32.455Z Last Updated: 2025-05-04T09:32:19.912Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/xe: reset mmio mappings with devm Set our various mmio mappings to NULL. This should make it easier to catch something rogue trying to mess with mmio after device removal. For example, we might unmap everything and then start hitting some mmio address which has already been unmamped by us and then remapped by something else, causing all kinds of carnage. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b1c9fbed3884d38
arnage. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b1c9fbed3884d3883021d699c7cdf5253a65543a - https://git.kernel.org/stable/c/c7117419784f612d59ee565145f722e8b5541fe6
CVE ID: CVE-2024-46706 State: PUBLISHED Published: 2024-09-13T06:27:33.085Z Last Updated: 2025-05-04T09:32:21.349Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tty: serial: fsl_lpuart: mark last busy before uart_add_one_port With "earlycon initcall_debug=1 loglevel=8" in bootargs, kernel sometimes boot hang. It is because normal console still is not ready, but runtime suspend is called, so early console putchar will hang in waiting TRDE set in UARTSTAT. The lpuart driver has auto suspend delay set to 3000ms, but during uart_add_one_port, a child device serial ctrl will added and probed with its pm runtime enabled(see serial_c
but during uart_add_one_port, a child device serial ctrl will added and probed with its pm runtime enabled(see serial_ctrl.c). The runtime suspend call path is: device_add |-> bus_probe_device |->device_initial_probe |->__device_attach |-> pm_runtime_get_sync(dev->parent); |-> pm_request_idle(dev); |-> pm_runtime_put(dev->parent); So in the end, before normal console ready, the lpuart get runtime suspended. And earlycon putchar will hang. To address the issue, mark last busy just after pm_runtime_enable, three seconds is long enough to switch from bootconsole to normal console. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/8eb92cfca6c2c5a15
sole. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/8eb92cfca6c2c5a15ab1773f3d18ab8d8f7dbb68 - https://git.kernel.org/stable/c/3ecf625d4acb71d726bc0b49403cf68388b3d58d - https://git.kernel.org/stable/c/dc98d76a15bc29a9a4e76f2f65f39f3e590fb15c
CVE ID: CVE-2024-46707 State: PUBLISHED Published: 2024-09-13T06:27:33.709Z Last Updated: 2025-11-03T22:16:36.453Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3 On a system with a GICv3, if a guest hasn't been configured with GICv3 and that the host is not capable of GICv2 emulation, a write to any of the ICC_*SGI*_EL1 registers is trapped to EL2. We therefore try to emulate the SGI access, only to hit a NULL pointer as no private interrupt is allocated (no GIC, remember?). The obvious fix is to give the guest what it deserves, in the shape of a UNDEF exception. A
located (no GIC, remember?). The obvious fix is to give the guest what it deserves, in the shape of a UNDEF exception. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/15818af2f7aa55eff375333cb7689df15d3f24ef - https://git.kernel.org/stable/c/96b076e8ee5bc3a1126848c8add0f74bd30dc9d1 - https://git.kernel.org/stable/c/94d4fbad01b19ec5eab3d6b50aaec4f9db8b2d8d - https://git.kernel.org/stable/c/9d7629bec5c3f80bd0e3bf8103c06a2f7046bd92 - https://git.kernel.org/stable/c/2073132f6ed3079369e857a8deb33d11bdd983bc - https://git.kernel.org/stable/c/3e6245ebe7ef341639e9a7e402b3ade8ad45a19f
CVE ID: CVE-2024-46708 State: PUBLISHED Published: 2024-09-13T06:33:40.510Z Last Updated: 2025-05-04T09:32:24.325Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: pinctrl: qcom: x1e80100: Fix special pin offsets Remove the erroneus 0x100000 offset to prevent the boards from crashing on pin state setting, as well as for the intended state changes to take effect. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/0197bf772f657fbdea5e9bdec5eea6e67d82cbde - https://git.kernel.org/stable/c/d3692d95cc4d88114b070ee63cffc976f00f207f
CVE ID: CVE-2024-46709 State: PUBLISHED Published: 2024-09-13T06:33:41.392Z Last Updated: 2025-05-04T12:58:39.549Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Fix prime with external buffers Make sure that for external buffers mapping goes through the dma_buf interface instead of trying to access pages directly. External buffers might not provide direct access to readable/writable pages so to make sure the bo's created from external dma_bufs can be read dma_buf interface has to be used. Fixes crashes in IGT's kms_prime with vgem. Regular desktop usage won't trigger this due to the fact that virtual machines will
ashes in IGT's kms_prime with vgem. Regular desktop usage won't trigger this due to the fact that virtual machines will not have multiple GPUs but it enables better test coverage in IGT. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/9a9716bbbf3dd6b6cbefba3abcc89af8b72631f4 - https://git.kernel.org/stable/c/5c12391ee1ab59cb2f3be3f1f5e6d0fc0c2dc854 - https://git.kernel.org/stable/c/50f1199250912568606b3778dc56646c10cb7b04
CVE ID: CVE-2024-46710 State: PUBLISHED Published: 2024-09-13T06:33:42.285Z Last Updated: 2025-11-03T22:16:37.924Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Prevent unmapping active read buffers The kms paths keep a persistent map active to read and compare the cursor buffer. These maps can race with each other in simple scenario where: a) buffer "a" mapped for update b) buffer "a" mapped for compare c) do the compare d) unmap "a" for compare e) update the cursor f) unmap "a" for update At step "e" the buffer has been unmapped and the read contents is bogus. Prevent unmapping of active read buffers by simply ke
p "e" the buffer has been unmapped and the read contents is bogus. Prevent unmapping of active read buffers by simply keeping a count of how many paths have currently active maps and unmap only when the count reaches 0. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/58a3714db4d9dcaeb9fc4905141e17b9f536c0a5 - https://git.kernel.org/stable/c/0851b1ec650adadcaa23ec96daad95a55bf966f0 - https://git.kernel.org/stable/c/d5228d158e4c0b1663b3983044913c15c3d0135e - https://git.kernel.org/stable/c/aba07b9a0587f50e5d3346eaa19019cf3f86c0ea
CVE ID: CVE-2024-46711 State: PUBLISHED Published: 2024-09-13T06:33:42.956Z Last Updated: 2025-11-03T22:16:39.367Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: fix ID 0 endp usage after multiple re-creations 'local_addr_used' and 'add_addr_accepted' are decremented for addresses not related to the initial subflow (ID0), because the source and destination addresses of the initial subflows are known from the beginning: they don't count as "additional local address being used" or "ADD_ADDR being accepted". It is then required not to increment them when the entrypoint used by the initial subflow is removed and re-added
pted". It is then required not to increment them when the entrypoint used by the initial subflow is removed and re-added during a connection. Without this modification, this entrypoint cannot be removed and re-added more than once. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c9c744666f7308a4daba520191e29d395260bcfe - https://git.kernel.org/stable/c/53e2173172d26c0617b29dd83618b71664bed1fb - https://git.kernel.org/stable/c/119806ae4e46cf239db8e6ad92bc2fd3daae86dc - https://git.kernel.org/stable/c/9366922adc6a71378ca01f898c41be295309f044
CVE ID: CVE-2024-46712 State: PUBLISHED Published: 2024-09-13T06:44:59.746Z Last Updated: 2025-05-04T09:32:30.179Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Disable coherent dumb buffers without 3d Coherent surfaces make only sense if the host renders to them using accelerated apis. Without 3d the entire content of dumb buffers stays in the guest making all of the extra work they're doing to synchronize between guest and host useless. Configurations without 3d also tend to run with very low graphics memory limits. The pinned console fb, mob cursors and graphical login manager tend to run out of 16MB graphics me
aphics memory limits. The pinned console fb, mob cursors and graphical login manager tend to run out of 16MB graphics memory that those guests use. Fix it by making sure the coherent dumb buffers are only used on configs with 3d enabled. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c45558414b8f2e0b9dc34eb8f9d4e8359b887681 - https://git.kernel.org/stable/c/e9fd436bb8fb9b9d31fdf07bbcdba6d30290c5e4
CVE ID: CVE-2024-46713 State: PUBLISHED Published: 2024-09-13T14:49:13.691Z Last Updated: 2025-11-03T22:16:42.290Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: perf/aux: Fix AUX buffer serialization Ole reported that event->mmap_mutex is strictly insufficient to serialize the AUX buffer, add a per RB mutex to fully serialize it. Note that in the lock order comment the perf_event::mmap_mutex order was already wrong, that is, it nesting under mmap_lock is not new with this patch. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/7882923f1cb88dc1a17f2bf0c81b
SA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/7882923f1cb88dc1a17f2bf0c81b1fc80d44db82 - https://git.kernel.org/stable/c/52d13d224fdf1299c8b642807fa1ea14d693f5ff - https://git.kernel.org/stable/c/9dc7ad2b67772cfb94ceb3b0c9c4023c2463215d - https://git.kernel.org/stable/c/c4b69bee3f4ef76809288fe6827bc14d4ae788ef - https://git.kernel.org/stable/c/b9b6882e243b653d379abbeaa64a500182aba370 - https://git.kernel.org/stable/c/2ab9d830262c132ab5db2f571003d80850d56b2a
CVE ID: CVE-2024-46714 State: PUBLISHED Published: 2024-09-18T06:32:14.852Z Last Updated: 2025-11-03T22:16:45.283Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Skip wbscl_set_scaler_filter if filter is null Callers can pass null in filter (i.e. from returned from the function wbscl_get_filter_coeffs_16p) and a null check is added to ensure that is not the case. This fixes 4 NULL_RETURNS issues reported by Coverity. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/0364f1f17a86d89dc39040beea4f099e60189f1b - https://git.kernel.org/stable/c/
eferences: - https://git.kernel.org/stable/c/0364f1f17a86d89dc39040beea4f099e60189f1b - https://git.kernel.org/stable/c/c083c8be6bdd046049884bec076660d4ec9a19ca - https://git.kernel.org/stable/c/6d94c05a13fadd80c3e732f14c83b2632ebfaa50 - https://git.kernel.org/stable/c/1726914cb17cedab233820d26b86764dc08857b4 - https://git.kernel.org/stable/c/e3a95f29647ae45d1ec9541cd7df64f40bf2120a - https://git.kernel.org/stable/c/54834585e91cab13e9f82d3a811deb212a4df786 - https://git.kernel.org/stable/c/c4d31653c03b90e51515b1380115d1aedad925dd
CVE ID: CVE-2024-46715 State: PUBLISHED Published: 2024-09-18T06:32:15.466Z Last Updated: 2025-11-03T22:16:46.735Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: driver: iio: add missing checks on iio_info's callback access Some callbacks from iio_info structure are accessed without any check, so if a driver doesn't implement them trying to access the corresponding sysfs entries produce a kernel oops such as: [ 2203.527791] Unable to handle kernel NULL pointer dereference at virtual address 00000000 when execute [...] [ 2203.783416] Call trace: [ 2203.783429] iio_read_channel_info_avail from dev_attr_show+0x18/0x48 [ 2203.78980
te [...] [ 2203.783416] Call trace: [ 2203.783429] iio_read_channel_info_avail from dev_attr_show+0x18/0x48 [ 2203.789807] dev_attr_show from sysfs_kf_seq_show+0x90/0x120 [ 2203.794181] sysfs_kf_seq_show from seq_read_iter+0xd0/0x4e4 [ 2203.798555] seq_read_iter from vfs_read+0x238/0x2a0 [ 2203.802236] vfs_read from ksys_read+0xa4/0xd4 [ 2203.805385] ksys_read from ret_fast_syscall+0x0/0x54 [ 2203.809135] Exception stack(0xe0badfa8 to 0xe0badff0) [ 2203.812880] dfa0: 00000003 b6f10f80 00000003 b6eab000 00020000 00000000 [ 2203.819746] dfc0: 00000003 b6f10f80 7ff00000 00000003 00000003 00000000 00020000 00000000 [ 2203.826619] dfe0: b6e1bc88 bed80958 b6e1bc94 b6e1bcb0 [ 2203.830363] Code: bad
03 00000003 00000000 00020000 00000000 [ 2203.826619] dfe0: b6e1bc88 bed80958 b6e1bc94 b6e1bcb0 [ 2203.830363] Code: bad PC value [ 2203.832695] ---[ end trace 0000000000000000 ]--- Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/0cc7e0ee31e5c44904e98e2229d591e093282a70 - https://git.kernel.org/stable/c/72f022ebb9deac28663fa4c04ba315ed5d6654d1 - https://git.kernel.org/stable/c/dc537a72f64890d883d24ae4ac58733fc5bc523d - https://git.kernel.org/stable/c/c4ec8dedca961db056ec85cb7ca8c9f7e2e92252
CVE ID: CVE-2024-46716 State: PUBLISHED Published: 2024-09-18T06:32:16.084Z Last Updated: 2025-11-03T22:16:48.183Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor Remove list_del call in msgdma_chan_desc_cleanup, this should be the role of msgdma_free_descriptor. In consequence replace list_add_tail with list_move_tail in msgdma_free_descriptor. This fixes the path: msgdma_free_chan_resources -> msgdma_free_descriptors -> msgdma_free_desc_list -> msgdma_free_descriptor which does not correctly free the descriptors as first nodes were not removed from th
esc_list -> msgdma_free_descriptor which does not correctly free the descriptors as first nodes were not removed from the list. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/a3480e59fdbe5585d2d1eff0bed7671583acf725 - https://git.kernel.org/stable/c/20bf2920a869f9dbda0ef8c94c87d1901a64a716 - https://git.kernel.org/stable/c/db67686676c7becc1910bf1d6d51505876821863 - https://git.kernel.org/stable/c/54e4ada1a4206f878e345ae01cf37347d803d1b1
CVE ID: CVE-2024-46717 State: PUBLISHED Published: 2024-09-18T06:32:16.791Z Last Updated: 2025-11-03T22:16:49.634Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: SHAMPO, Fix incorrect page release Under the following conditions: 1) No skb created yet 2) header_size == 0 (no SHAMPO header) 3) header_index + 1 % MLX5E_SHAMPO_WQ_HEADER_PER_PAGE == 0 (this is the last page fragment of a SHAMPO header page) a new skb is formed with a page that is NOT a SHAMPO header page (it is a regular data page). Further down in the same function (mlx5e_handle_rx_cqe_mpwrq_shampo()), a SHAMPO header page from header_index is released.
her down in the same function (mlx5e_handle_rx_cqe_mpwrq_shampo()), a SHAMPO header page from header_index is released. This is wrong and it leads to SHAMPO header pages being released more than once. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/03924d117625ecb10ee3c9b65930bcb2c37ae629 - https://git.kernel.org/stable/c/ae9018e3f61ba5cc1f08a6e51d3c0bef0a79f3ab - https://git.kernel.org/stable/c/c909ab41df2b09cde919801c7a7b6bb2cc37ea22 - https://git.kernel.org/stable/c/70bd03b89f20b9bbe51a7f73c4950565a17a45f7
CVE ID: CVE-2024-46718 State: PUBLISHED Published: 2024-09-18T06:32:17.412Z Last Updated: 2025-05-04T09:32:38.242Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/xe: Don't overmap identity VRAM mapping Overmapping the identity VRAM mapping is triggering hardware bugs on certain platforms. Use 2M pages for the last unaligned (to 1G) VRAM chunk. v2: - Always use 2M pages for last chunk (Fei Yang) - break loop when 2M pages are used - Add assert for usable_size being 2M aligned v3: - Fix checkpatch Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/bb706e92c87beb9f2543faa1705ccc330
Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/bb706e92c87beb9f2543faa1705ccc330b9e7c65 - https://git.kernel.org/stable/c/6d3581edffea0b3a64b0d3094d3f09222e0024f7
CVE ID: CVE-2024-46719 State: PUBLISHED Published: 2024-09-18T06:32:18.028Z Last Updated: 2025-11-03T22:16:52.599Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: Fix null pointer dereference in trace ucsi_register_altmode checks IS_ERR for the alt pointer and treats NULL as valid. When CONFIG_TYPEC_DP_ALTMODE is not enabled, ucsi_register_displayport returns NULL which causes a NULL pointer dereference in trace. Rather than return NULL, call typec_port_register_altmode to register DisplayPort alternate mode as a non-controllable mode when CONFIG_TYPEC_DP_ALTMODE is not enabled. Additional Analyst Notes: - CISA
alternate mode as a non-controllable mode when CONFIG_TYPEC_DP_ALTMODE is not enabled. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8095bf0579ed4906a33f7bec675bfb29b6b16a3b - https://git.kernel.org/stable/c/7e64cabe81c303bdf6fd26b6a09a3289b33bc870 - https://git.kernel.org/stable/c/3aa56313b0de06ce1911950b2cc0c269614a87a9 - https://git.kernel.org/stable/c/b4243c05d7e3db0bdbf9124e6fa59b4ca7c807ae - https://git.kernel.org/stable/c/3b9f2d9301ae67070fe77a0c06758722fd7172b7 - https://git.kernel.org/stable/c/99331fe68a8eaa4097143a33fb0c12d5e5e8e830 - https://git.kernel.org/stable/c/99516f76db48e1a9d54cdfed63c1babcee4e71a5
CVE ID: CVE-2024-46720 State: PUBLISHED Published: 2024-09-18T06:32:18.695Z Last Updated: 2025-11-03T22:16:54.084Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix dereference after null check check the pointer hive before use. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/1b73ea3d97cc23f9b16d10021782b48397d2b517 - https://git.kernel.org/stable/c/0aad97bf6d0bc7a34a19f266b0b9fb2861efe64c - https://git.kernel.org/stable/c/00b9594d6310eb33e14d3f07b54866499efe0d50 - https://git.kernel.org/stable/c/b1f7810b05d1950350ac2e06992982974343e441
CVE ID: CVE-2024-46721 State: PUBLISHED Published: 2024-09-18T06:32:19.327Z Last Updated: 2025-11-03T22:16:57.048Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: apparmor: fix possible NULL pointer dereference profile->parent->dents[AAFS_PROF_DIR] could be NULL only if its parent is made from __create_missing_ancestors(..) and 'ent->old' is NULL in aa_replace_profiles(..). In that case, it must return an error code and the code, -ENOENT represents its state that the path of its parent is not existed yet. BUG: kernel NULL pointer dereference, address: 0000000000000030 PGD 0 P4D 0 PREEMPT SMP PTI CPU: 4 PID: 3362 Comm: apparmor_p
kernel NULL pointer dereference, address: 0000000000000030 PGD 0 P4D 0 PREEMPT SMP PTI CPU: 4 PID: 3362 Comm: apparmor_parser Not tainted 6.8.0-24-generic #24 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 RIP: 0010:aafs_create.constprop.0+0x7f/0x130 Code: 4c 63 e0 48 83 c4 18 4c 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 c3 cc cc cc cc <4d> 8b 55 30 4d 8d ba a0 00 00 00 4c 89 55 c0 4c 89 ff e8 7a 6a ae RSP: 0018:ffffc9000b2c7c98 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 00000000000041ed RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000b2c7cd8 R08: 0000000000000000
0000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000b2c7cd8 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff82baac10 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007be9f22cf740(0000) GS:ffff88817bc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000030 CR3: 0000000134b08000 CR4: 00000000000006f0 Call Trace: <TASK> ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? kernelmode_fixup_or_oops+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2c0 ? find_vma+0x34/0x60 ? bad_area_nosemaphore+0x16/0x30 ? do_user_addr_fa
+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2c0 ? find_vma+0x34/0x60 ? bad_area_nosemaphore+0x16/0x30 ? do_user_addr_fault+0x2a2/0x6b0 ? exc_page_fault+0x83/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? aafs_create.constprop.0+0x7f/0x130 ? aafs_create.constprop.0+0x51/0x130 __aafs_profile_mkdir+0x3d6/0x480 aa_replace_profiles+0x83f/0x1270 policy_update+0xe3/0x180 profile_load+0xbc/0x150 ? rw_verify_area+0x47/0x140 vfs_write+0x100/0x480 ? __x64_sys_openat+0x55/0xa0 ? syscall_exit_to_user_mode+0x86/0x260 ksys_write+0x73/0x100 __x64_sys_write+0x19/0x30 x64_sys_call+0x7e/0x25c0 do_syscall_64+0x7f/0x180 entry_SYSCALL_64_after_hwframe+0x78/0x80 RIP: 0033:0x7be9f211c574 Code: c7 00 16 00 00 00 b8 ff ff f