# A Linux kernel flaw freezes 119.9 million in Aave

> A Linux kernel flaw left operators unable to sign and froze 119.9 million in Aave: the bridge came back on November 8 and the app is still down.
> By José Maldonado · DeFi · 2026-11-09

The 119.9 million dollars that Aave holds in its Ethereum Core market against tBTC have been unable to grow for nine days, and the reason is not a hack or a bankruptcy: it is a Linux kernel vulnerability that forced nodes to be shut down. Threshold, the network that issues the token, paused new deposits, minting and redemptions on October 31, and this November 9 the reserve remains frozen. No private keys were lost and no Aave contract broke.

tBTC is a token that represents bitcoin and is issued through a bridge with independent operators. Moving a single satoshi out of the reserve requires the signatures of a majority of those operators, so none of them can withdraw the funds on their own. When that majority shuts down its machines to patch the kernel, signing stops even though the money stays where it was and the backing remains intact against the 4,320.58 BTC that the network explorer showed this week.

The frozen figure is large, and the lesson it leaves is even larger: an operating system maintenance window, decided by administrators who never spoke to Aave, can shut down a market of 119.9 million without anyone having attacked anything.

## The timeline since October 31

Threshold [announced](https://x.com/TheTNetwork/status/2116588948881375583) the pause on October 31 with effects on three fronts at once: new BTC deposits, tBTC minting and redemptions. Two days later, its security update explained the cause that nobody expected in a bridge: all nodes were patched or offline because operators were dealing with a Linux kernel vulnerability. The October 31 pause announcement and the November 2 report sketch out an interruption that began with the operating system and not with the protocol's code.

Threshold described the state of its nodes with a phrase that deserves attention: all patched or offline, without exceptions. An operator dealing with the kernel advisory could apply the update and come back, or shut down and wait, and in both cases stopped signing for a while. The bridge did not go down because of an attack; it was left without a quorum due to maintenance.

LlamaRisk opened a thread on Aave's governance forum on October 31 itself to request the freeze of the tBTC market on Ethereum Core. Its argument was to limit the protocol's exposure to tBTC for as long as the interruption lasted, and governance applied it to a reserve that at that moment was worth 119.9 million dollars. Nine days later, that figure is still the same and the thread still has no closing date.

Neither of the two notices set a date for the end of the problem or gave the identifier of the kernel flaw. That silence is normal in an open incident and it is also what prevents users from calculating when they will be able to redeem their tBTC.

## The kernel as the root cause of a freeze in DeFi

The kernel is the piece of software that talks to the hardware, so a bitcoin bridge depends on it as much as on its own code. tBTC operators run their own nodes, each with its own distribution, its own update cycle and its own schedule. A vulnerability that threatens them all at once pushes them to patch at once, and while the patch is being applied the majority of signatures the bridge needs does not exist.

The pressure is not theoretical. The kernel sees a steady drip of CVEs that no longer fits into a manual review, as shown by the [count of flaws that the kernel cannot keep up with triaging](https://observatorioblockchain.com/en/cybersecurity/kernel-linux-avalancha-cve-triaje-ia/). The [CVE-2026-98432 in IPv4 TCP](https://observatorioblockchain.com/en/cybersecurity/cve-2026-98432-kernel-tcp-ubuntu-rhel-sin-parche/) he added the opposite case: a patch on the stable branches and a three-week wait on Ubuntu and RHEL, with administrators deciding whether to update or hold out.

A bridge boasts that its operators are independent, and they are as long as they do not share the same obligation to update. The model's independence is measured in signers, and the kernel does not distinguish between signers.

## A frozen reserve

Aave is a lending market where you deposit one asset and borrow another against it, with the collateral posted in the first. Freezing the tBTC reserve does not touch positions that already exist: anyone with debt against tBTC can keep repaying it, anyone who lent can withdraw and liquidators can close positions with compromised health. What is closed is entry, that is, new tBTC supply and new loans taken against it.

The tokens remain transferable, so the secondary market did not stop with the freeze. Anyone who wants out can sell tBTC there instead of waiting for redemption, and takes whatever price that market sets. Anyone hoping to recover their bitcoins through the normal route depends on more operators reconnecting, and there is no public timetable or promised deadline for that.

Liquidation deserves a clarification because it sounds like a punishment and is not. If a user's loan falls below the required collateral threshold, a third party can close the debt and keep the collateral at the discount set by the protocol, and with the reserve frozen that valve remains active. Without it, a price drop would leave debts uncovered and the market would pay for the freeze with losses instead of with waiting. That mechanism is what separates an orderly pause from a broken market.

The freeze reduces Aave's new exposure, not the risk of what is already inside. If tBTC's backing holds, the pause closes without losses; if it stopped holding, the frozen reserve would be the problem and not the solution.

## The bridge came back and the app did not

Threshold [reopened](https://x.com/TheTNetwork/status/2119568052064751922) on-chain operations on November 8, and the app is still waiting for more operators to reconnect. The bridge's post-reopening report describes a network that already processes on-chain operations and an interface that still does not allow redemptions, with no date for resuming them. The difference matters because a redemption does not start on-chain, but with a request the app has to accept.

Threshold maintains that tBTC is fully backed, and the network explorer showed about 4,320.58 BTC against the $119.9 million frozen in the Aave Ethereum Core reserve. The notice for those with funds in transit gives two specific instructions: do not send BTC to deposit addresses generated before the pause and do not resend pending transactions, because the bridge may have processed them or may have discarded them.

The distinction between the chain and the app looks like a technical nuance and is not. The chain does not ask anyone's permission; the app is the gate that decides who gets in, and that gate has been closed for nine days.

## Dependence on shared infrastructure

DeFi presents itself as an autonomous layer and is not. Every protocol relies on servers, node providers, data links between chains and an operating system that someone has to update by hand. The [dependency pattern that Tendril and CoreVault broke](https://observatorioblockchain.com/en/defi/tendril-corevault-exploit-seguro-defi/) attacked the price a contract read within the same transaction; this case attacks something duller and deeper, the machine that signs the transactions.

A bridge's risk is no longer measured only by its code or by the size of its signer committee. It also counts how many of those signers update in time, how many can stay online with the patched kernel and how long the rest take to sign again. That figure appears in no contract audit, and in this incident it is the only one that decided when the bridge reopens. The network's public reports speak of operators still to be reconnected, without giving the number or the deadline, and that vagueness is itself the most useful information for the user.

Today the useful question is not whether tBTC is backed, which Threshold maintains and the explorer figure supports, but how many operators have returned and when redemptions reopen. Until there is an answer, Aave's $119.9 million will stay frozen.
