{"api_version":"1","generated_at":"2026-08-25T02:10:33+00:00","cve":"CVE-2026-68177","urls":{"html":"https://cve.report/CVE-2026-68177","api":"https://cve.report/api/cve/CVE-2026-68177.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-68177","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-68177"},"summary":{"title":"tracing: Delay module ref count for \"enable_event\" trigger","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Delay module ref count for \"enable_event\" trigger\n\nTriggers are now delayed from freeing, but can still be triggered until\nafter the RCU grace period has ended. The freeing of the enable_event data\nis put into the private_data_free() callback, but the put of the module\nrefcount is done immediately.\n\nIt is possible that if a module is removed that has an event that would\nenable (or disable) it is still active, it can read the data of the module\nafter it is removed causing a use-after-free bug.\n\nMove the trace_event_put_ref() that releases the module into the delayed\ncallback so that the module can not be removed until any reference to its\nevents are finished.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-10 13:20:04","updated_at":"2026-08-17 05:18:19"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/e091351b38818ef620d27f44f4bfd625f13afbff","name":"https://git.kernel.org/stable/c/e091351b38818ef620d27f44f4bfd625f13afbff","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/159fdc3e01dca5fdbc412fcd8b239895733a270d","name":"https://git.kernel.org/stable/c/159fdc3e01dca5fdbc412fcd8b239895733a270d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-68177","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68177","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 61d445af0a7c70018111919e47beaaee15653f2f 159fdc3e01dca5fdbc412fcd8b239895733a270d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 61d445af0a7c70018111919e47beaaee15653f2f e091351b38818ef620d27f44f4bfd625f13afbff git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.6 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"68177","cve":"CVE-2026-68177","epss":"0.001540000","percentile":"0.050500000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:47"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/trace/trace_events_trigger.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"159fdc3e01dca5fdbc412fcd8b239895733a270d","status":"affected","version":"61d445af0a7c70018111919e47beaaee15653f2f","versionType":"git"},{"lessThan":"e091351b38818ef620d27f44f4bfd625f13afbff","status":"affected","version":"61d445af0a7c70018111919e47beaaee15653f2f","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/trace/trace_events_trigger.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.19"},{"lessThan":"6.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.6","versionStartIncluding":"6.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Delay module ref count for \"enable_event\" trigger\n\nTriggers are now delayed from freeing, but can still be triggered until\nafter the RCU grace period has ended. The freeing of the enable_event data\nis put into the private_data_free() callback, but the put of the module\nrefcount is done immediately.\n\nIt is possible that if a module is removed that has an event that would\nenable (or disable) it is still active, it can read the data of the module\nafter it is removed causing a use-after-free bug.\n\nMove the trace_event_put_ref() that releases the module into the delayed\ncallback so that the module can not be removed until any reference to its\nevents are finished."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The bug is reached only via local `write()` to tracefs event `trigger` files to register/remove `enable_event`/`disable_event` triggers and via local `delete_module(2)`/`rmmod` to unload the referenced trace-event module; no network, adjacent, or physical input path reaches `event_enable_trigger_free()` or `event_enable_trigger()`.\nAC:L - The attacker controls both sides of the race: one thread removes the trigger (premature `trace_event_put_ref()`) and unloads the module while another continuously fires the bound source tracepoint, exploiting the deferred-free window before `tracepoint_synchronize_unregister()` completes in the trigger cleanup kthread.\nPR:L - Trigger registration/removal is gated only by tracefs DAC and `LOCKDOWN_TRACEFS` without `capable()`, which Android/ChromeOS/Perfetto and tracing-group mounts grant to ordinary users; unloading the held module is achievable with `CAP_SYS_MODULE` in a user namespace on permissive kernels loading attacker-controlled modules.\nUI:N - The attacker performs trigger setup/removal, module unload, and source-event generation from their own threads; no separate victim user action is required once tracefs and module privileges are available.\nS:U - The use-after-free corrupts kernel heap/trace structures within the same OS security authority and does not cross a VM, IOMMU, or sandbox boundary.\nC:H - After premature `trace_event_put_ref()` permits module removal, in-flight `event_enable_trigger()`/`event_enable_count_func()` dereference freed `trace_event_file` and module-resident `trace_event_call` data, exposing reclaimed kernel heap contents.\nI:H - `event_enable_trigger()` performs `set_bit`/`clear_bit` on `enable_data->file->flags` through a pointer to a kmem_cache-freed `trace_event_file`, giving a controllable kernel write primitive via heap shaping.\nA:H - Dereferencing freed module/event-file memory from tracepoint context readily causes kernel oops/panic, and the attacker can repeat the race at will."}]}],"providerMetadata":{"dateUpdated":"2026-08-17T05:00:18.452Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/159fdc3e01dca5fdbc412fcd8b239895733a270d"},{"url":"https://git.kernel.org/stable/c/e091351b38818ef620d27f44f4bfd625f13afbff"}],"title":"tracing: Delay module ref count for \"enable_event\" trigger","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-68177","datePublished":"2026-08-10T11:59:48.318Z","dateReserved":"2026-07-30T09:28:09.373Z","dateUpdated":"2026-08-17T05:00:18.452Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-10 13:20:04","lastModifiedDate":"2026-08-17 05:18:19","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"68177","Ordinal":"1","Title":"tracing: Delay module ref count for \"enable_event\" trigger","CVE":"CVE-2026-68177","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"68177","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Delay module ref count for \"enable_event\" trigger\n\nTriggers are now delayed from freeing, but can still be triggered until\nafter the RCU grace period has ended. The freeing of the enable_event data\nis put into the private_data_free() callback, but the put of the module\nrefcount is done immediately.\n\nIt is possible that if a module is removed that has an event that would\nenable (or disable) it is still active, it can read the data of the module\nafter it is removed causing a use-after-free bug.\n\nMove the trace_event_put_ref() that releases the module into the delayed\ncallback so that the module can not be removed until any reference to its\nevents are finished.","Type":"Description","Title":"tracing: Delay module ref count for \"enable_event\" trigger"}]}}}