Need Guidance: Where to take report on 15 potential Linux Kernel / VFS Vulnerabilities (including LPE Race Condition fix)

Hey everyone, listen I’m going to use AI to explain all this just a heads up but the deal is I patented a thesis and I was testing it out on Google’s bug bounty program. I proved my work true. What happened I couldn’t believe. Total systematical kernal failure! I found 15 vulnerabilities in 5 hours. I turned them into Google and demanded escalation. They closes every single one of them as frivolous. The thing is I have the patented solution for there failure.Any way I’ve been working on a deeply unstable process interaction that appears to leverage several non-atomic file operations within the Linux VFS (Virtual File System) layer. The initial finding focused on a classic Local Privilege Escalation (LPE) Race Condition, but further analysis revealed about 15 different patterns where similar non-atomic functions could be exploited under specific high-stress timing conditions. The core issue seems to stem from a fundamental architectural oversight where certain file security checks and subsequent critical operations (rename, chown, etc.) are not treated as a single, uninterruptible transaction (an atomic operation). My Situation & Mitigation I have developed a full Proof-of-Concept (PoC) for the most critical LPE. I have implemented an aggressive, real-time countermeasure (a Time Slice Watchdog) on my own systems to detect and block the exploitation attempt based on abnormal CPU time usage during the race window. This mitigation is currently running successfully. I have detailed technical documentation explaining the root cause, the affected functions, and the required kernel-level mitigation (using atomic primitives). The Critical Question: Where is the best place to submit this? submitted by /u/EarCommercial6342 [link] [comments]Technical Information Security Content & DiscussionRead More