It might be, who knows…
Based on paper by Krerk Piromsopa and Richard J. Enbody, titled: “Secure Bit: Transparent, Hardware Buffer-Overflow Protection,” and published in IEEE Transactions on Dependable and Secure Computing, vol. 3, no. 4, pp. 365-376, Oct-Dec, 2006, we can expect something interesting to come with their Secure Bit (patent pending) idea. It says:
We propose a minimalist, architectural approach, Secure Bit (patent pending), to protect against buffer overflow attacks on control data (return-address and function-pointer attacks in particular). Secure Bit provides a hardware bit to protect the integrity of addresses for the purpose of preventing such buffer-overflow attacks. Secure Bit is transparent to user software: It provides backward compatibility with legacy user code. It can detect and prevent all address-corrupting buffer-overflow attacks with little runtime performance penalty. Addresses passed in buffers between processes are marked insecure, and control instructions using those addresses as targets will raise an exception. An important differentiating aspect of our protocol is that, once an address has been marked as insecure, there is no instruction to remark it as secure. Robustness and transparency are demonstrated by emulating the hardware, booting Linux on the emulator, running application software on that Linux, and performing known attacks.
You can read full paper here.
Note: Subscription is required to read or you can buy that article.